MAPI Error 22022 in SQL Server 2000

When I try to test the ability to send e-mail to an operator on one of my servers by opening up the properties for the operator and clicking the "test" button, I get the following error:

"Error 22022: SQLServerAgent Error: MAPI error: Table too big."

Has anyone encountered this? What's the resolution?

Can you log in to the server using the same account that the SQL Server Agent is using and send emails that way? If so, try deleting and recreating the pst file for that user.

BTW - you'll likely receive more feedback from another group. This one is dedicated to Notification Services, which despite the similar sounding name, is a completely different technology.

HTH...

Joesql

MAPI Error 22022 in SQL Server 2000

When I try to test the ability to send e-mail to an operator on one of my servers by opening up the properties for the operator and clicking the "test" button, I get the following error:

"Error 22022: SQLServerAgent Error: MAPI error: Table too big."

Has anyone encountered this? What's the resolution?

Can you log in to the server using the same account that the SQL Server Agent is using and send emails that way? If so, try deleting and recreating the pst file for that user.

BTW - you'll likely receive more feedback from another group. This one is dedicated to Notification Services, which despite the similar sounding name, is a completely different technology.

HTH...

Joe

Managing Connections for optimal performance question, switch from Oracle to SQL

I was told in one of my systems classes that the real performance bottleneck in accessing information from the database was the opening of a connection from the application to the database.

To combat that problem I was advised to use a Singleton Factory pattern and to have that Factory instaniate a connection and open it, then pass references to that connection for all of the objects that it created. All of those objects passed the connection reference to the objects they created and so on. Basically that meant that I only ever had one connection open at any one time for my entire application. And I was able to implement this solution at my previous job where I was developing in Oracle. I primarially used OracleCommands and OracleDataReaders to get the informaton into and out of the database. I thought this was a very nice solution. Having this many DataReaders accessing a single connection was not a problem because OracleConnections don't get locked from having more than one DataReader open at once.

At my current job, however, I use SQL Server. I am concerned that the single connection will not work in my new enviroment as the SQLDataReaders lock up the connection while they are using it. If the information that I recieved about opening connections being the real bottleneck, then I am hesitant to have a connection instanciated and opened for each method, but I am concerned that a whole lot of errors will be generated if I use the single connection method. Also, how do DataAdapters effect my decision of which approach to use.

Any advice would be most helpful. If you have any questions that would help answer just ask. Thanks.No! Definitely not the way to do it. Just use ADO.NET's connection pooling to manage it. Out of the box it's pretty efficient, but you can tweak it if necessary. There's no way you'll write anything that will be as efficient as what's already there.

You're right that a data reader hogs a connection.

And the decision is the same whether you use data adapters or readers.

Don|||How do I use ADO.Net's connection pooling? Is there an article or something that you know about that can teach me to manage this problem better.

Thanks again for your help.|||That connection pooling stuff is pretty cool. My systems class was based on Java so apparantly that type of behind the scenes work didn't take place to efficiently manage the connections. I didn't realize that when I was instanciating a connection it was already managing a pool of connections for me. slick stuff.|||So you figured out how to use it? Cool. Yeah, it definitely is an area where all of Microsoft's hard work is paying off.

Don

Management Studio: when opening a table, any way to sort the table ?

In SQL Server 2000 Enterprise Manager when you open a table you can open it
with a query "order by" to sort the table by a column.
In the SQL Server 2005 Management Studio when you open a table, is there any
way to sort it by any of the column ?
Thank you
> In the SQL Server 2005 Management Studio when you open a table, is there
> any way to sort it by any of the column ?
My suggestion is to write...
SELECT * FROM table_name ORDER BY column_name;
...in a Query Editor window. Open Table is a bad joke.
|||I'll second that Aaron!
TheSQLGuru
President
Indicium Resources, Inc.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:eFIRE0TrHHA.1172@.TK2MSFTNGP03.phx.gbl...
> My suggestion is to write...
> SELECT * FROM table_name ORDER BY column_name;
> ...in a Query Editor window. Open Table is a bad joke.
>
|||Thank you.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ukOnG1TrHHA.1296@.TK2MSFTNGP06.phx.gbl...
> Yes - click on the buttons in the top left hand corner to get the SQL,
> Diagram and Criteria. You can do the sorting by selecting the column in
> the diagram (check the box) then select the ascending/descending option in
> the grid for the column. Alternatively just code the SQL directly in the
> SQL pane.
> HTH,
> Paul Ibison
>

Management Studio: when opening a table, any way to sort the table ?

In SQL Server 2000 Enterprise Manager when you open a table you can open it
with a query "order by" to sort the table by a column.
In the SQL Server 2005 Management Studio when you open a table, is there any
way to sort it by any of the column ?
Thank you> In the SQL Server 2005 Management Studio when you open a table, is there
> any way to sort it by any of the column ?
My suggestion is to write...
SELECT * FROM table_name ORDER BY column_name;
...in a Query Editor window. Open Table is a bad joke.|||Yes - click on the buttons in the top left hand corner to get the SQL,
Diagram and Criteria. You can do the sorting by selecting the column in the
diagram (check the box) then select the ascending/descending option in the
grid for the column. Alternatively just code the SQL directly in the SQL
pane.
HTH,
Paul Ibison|||I'll second that Aaron!
TheSQLGuru
President
Indicium Resources, Inc.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in mess
age
news:eFIRE0TrHHA.1172@.TK2MSFTNGP03.phx.gbl...
> My suggestion is to write...
> SELECT * FROM table_name ORDER BY column_name;
> ...in a Query Editor window. Open Table is a bad joke.
>|||Thank you.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ukOnG1TrHHA.1296@.TK2MSFTNGP06.phx.gbl...
> Yes - click on the buttons in the top left hand corner to get the SQL,
> Diagram and Criteria. You can do the sorting by selecting the column in
> the diagram (check the box) then select the ascending/descending option in
> the grid for the column. Alternatively just code the SQL directly in the
> SQL pane.
> HTH,
> Paul Ibison
>

Management Studio: when opening a table, any way to sort the table ?

In SQL Server 2000 Enterprise Manager when you open a table you can open it
with a query "order by" to sort the table by a column.
In the SQL Server 2005 Management Studio when you open a table, is there any
way to sort it by any of the column ?
Thank you> In the SQL Server 2005 Management Studio when you open a table, is there
> any way to sort it by any of the column ?
My suggestion is to write...
SELECT * FROM table_name ORDER BY column_name;
...in a Query Editor window. Open Table is a bad joke.|||Yes - click on the buttons in the top left hand corner to get the SQL,
Diagram and Criteria. You can do the sorting by selecting the column in the
diagram (check the box) then select the ascending/descending option in the
grid for the column. Alternatively just code the SQL directly in the SQL
pane.
HTH,
Paul Ibison|||I'll second that Aaron!
--
TheSQLGuru
President
Indicium Resources, Inc.
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:eFIRE0TrHHA.1172@.TK2MSFTNGP03.phx.gbl...
>> In the SQL Server 2005 Management Studio when you open a table, is there
>> any way to sort it by any of the column ?
> My suggestion is to write...
> SELECT * FROM table_name ORDER BY column_name;
> ...in a Query Editor window. Open Table is a bad joke.
>|||Thank you.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ukOnG1TrHHA.1296@.TK2MSFTNGP06.phx.gbl...
> Yes - click on the buttons in the top left hand corner to get the SQL,
> Diagram and Criteria. You can do the sorting by selecting the column in
> the diagram (check the box) then select the ascending/descending option in
> the grid for the column. Alternatively just code the SQL directly in the
> SQL pane.
> HTH,
> Paul Ibison
>

Management Studio Sluggish

We have noticed that quite frequently, SQL Server Management Studio is somewhat sluggish with expanding lists for tables, opening stored procedures, opening files, etc.

Executing queries seems to be very quick though.

The machine that has SQL 2005 is 2.8 GHz with 512 MB of RAM.

Any idea why SQL Server Management Studio would seem somewhat sluggish?

That is really not very much memory for SQL Server (and the OS). I recommend adding additional memory and comparing the times -I think you will be pleased with the effect.|||Thanks. Got the order from the boss to bump it up to 2.5 GIG ram. I'll let you know how it performs after the upgrade.