In short, no, on SQL 2000 you will not be able to tell if/when/who dropped a table. Your only option is to restore the table from a backup...if such...

It should work with no problems. Provided the disks are presented to SQL as they look today. The identifier is only a worry in a clustered configuration, and...

The biggest advantage for going to Server 2003 over Server 2000, is that 2000 is on life support as MSFT, 2003 is in the ICU. If you are going...

Add the second node.

Under configuration mgr, go to TCP/IP properties, make sure that each SQL Server is listening on 1433 on the public address (don't worry at all about the...

There are certain T-SQL commands that are no longer supported with SQL2008, what comes to mind is the command DUMP (left over from the Sybase days), there may be some...

Do a backup on the 2005 server, copy the backup to the 2008 server, restore the backup.

If the DB if fully 2008 compliant, change the compatibility from 90 to 10.

There...

Thanks, yeah, I gues I did

here is the article to import the log

http://www.databasejournal.com/scripts/article.php/3518116/Import-the-SQL-Server-Error-Log-into-a-Table.htm

Memory and caching are far more complicated than that. There are other db's on the server, execution plans are cached, indexes, etc... Just leave your memory setting where...

You can create a job that reads the errorlog every five minutes (insert the errorlog into a temp table), if there's a deadlock in the last five minutes (or one...

Since when did the S get added? I now see it on other servers, I guess I just had not noticed it before. It seems to be dumbing...

Just try something like

set @ServerName = lower(@ServerName)

set @ServerName2 = upper(left(@ServerName,1)) + right(@ServerName, (len(@ServerName)-1))

That should then be upper case first letter, lower case, all the other letters

There is no one answer. I've worked with OLTP systems that had over 2 billion rows in a frequently accessed table with few problems, I've worked with DW's that...

Don't create a maintenance plan. Just create a job with T-SQL.

In the job do a backup database to <<NAME>>

Just write disk = '<<DBNAME>>.BAK'

Then restore the same name nightly, it...

Let's keep in mind we are comparing client OS's. There are so many things that corporate PC/LAN add's to clients. It's an interesting comparison in theory, but not...

Are you planning on running SQL 2008 on Windows 2000 or are you planning on upgarding the OS?

Generally 2008 will require resources, as it has more capabilities.

The default server trace...