If you are really wanting to look at compression on heavily used tables you might want to consider ROW level rather than PAGE level. You obviously won't get the same...

Additionally, check to make sure that the SPN is registered correctly.

I've had no problems either. Just be aware that there are certain caveats as regards data types and compression, check out http://msdn.microsoft.com/en-us/library/ms143241.aspx for more info.

You have SQL Agent setup to use the localsystem account which does not have access to remote resources (ie the share on the app server).

You'll need to change the Agent...

Check the security settings on your remote share to see if the SQL Server Agent account has the access you need.

Paul White (3/10/2010)

Lynn Pettis (3/10/2010)

Paul White (3/10/2010)

C'mon guys, think outside of the box! ...

What might help is creating a proc sp_send_cdosysmail and calling sp_send_dbmail from it thereby not having to adjust the existing code you have calling sp_send_cdosysmail.

If you're running Enterprise Edition then don't forget to set Lock Pages in Memory.

It could be any number of things.

You need to take a look at the way memory and cpu are being handled, whether it's the page draw that's causing the issues,...

And...you are trying to returns 59k records to the web server?

You need to have at least one disk available that is not assigned elsewhere.

You can put all of the SQL resources on that one disk (obviously not recommended) should you...

Regional keyboards are brutal. These windows admins, they'll kill you every time :hehe:

That is worth a blog post or article right there.

How did you ultimately discover this?

It very much depends upon whether you are going to be running things like replication and how many connections you expect to have, whether you have SSIS packages executing etc.

Working...

Just want to confirm, you are able to login from one machine using the sa account however you get a failure when attempting to use the same sa login from...