Yeah, I think I found out what is causing it.  Our hosting provider is running backups well past their window.  Not sure why yet, but at least I know the...

I have ours set with min/max memory and turned on working set = 1.  It seems to be good.  However, you are exactly right...if you NEED to swap the memory...

another way is to simply issue:

sp_help '<tablename>' where <tablename is the name of your table.

The biggest difference is ServerProperty('ServerName') reports network name.  @@Servername does not.

So my understanding is if you change the name of your SQL Server, it will not be reflected with @@Servername...

Very nice.

I just updated the pe nformance counters as I inserted them so that they would already have the correct value.

To get server uptime, I just used tempdb creation date/time. ...

I think I found my own answer.

Its a Microsoft bug.  Does anyone have a good work around to get these values reflected properly?

See MS Article:  http://support.microsoft.com/default.aspx?scid=kb;en-us;555064

I too am havinga  similiar problem but it is not a maintenance job.

I'm simply trying to delete rows from a table where a field is null. (the field is varchar(7000).

Please...

I can answer a couple.

Tempdb shrink should not be too much of a problem assuming that you have fast disks.  Use statistics io to monitor.

For moving your db, try...

As a general rule, you can figure about 2 times the size of the original field, * number of rows * number of tables.

This will ballpark you i think.  Remember, to...

I think that partioning is a good solution, should you be working with large tables.  If the tables are very large, it will allow you to get smaller.

By partioning the...

First off, this is probably a really bad idea.  However, if you still want to do it, then so be it. Denormalization of data causes a number of anamolies and...

Given that you know the entire path of the file, you should be able to add (to your procedure) an xp_cmdshell call to delete the file. 

However, security is of the...

We just experienced the same problem.

The possibility of that the following occured:  We created databases while the SQL Server was in DOMAINA.  We then moved the SQL Server to DOMAINB. ...