I have not much exposure of VMWare.

But if we think logically I won't perfer to run production on VMWare on follwoing ground:

1. It will share the resources like CPU,...

Hello Paul,

FYI:

I was using sql server 7.0 standard edition RAM 2.0 GB. Memory setting Dynamic. Now we have upgraded the server to 4.0 GB.

After the memory upgrade the problem...

Looks like memory leak problem:

refer the sql server and do the AWE settings as per the articles

http://support.microsoft.com/kb/274750

Make sure you are using sql server enterprise edition; else assign sql...

You can design DTS package (SSIS) to do insert / delete operation and schedule DTS package.

In my openion both command do the same thing one shrinkfile will shrink single file while shrinkdatabase will shrink the set of files in the database. Also after executing any...

Microsoft itself is using Lightspeed to backup their VLDB databases. Hence I won't hesitate to go with Lightspeed.

But if you are looking something more beyond only Backup/Restore and to...

What is the database size? Make sure you do have enough space for the backup. Generally once backup starts will completed successfully.

Workaround:

You can use SSIS and transfer table from SQL Server 2000 to SQL Server 2005 instead of text file.

I also face the similar kind of problem:

When the table size is very small and contain a few rows only at that time this kind of problem happen. In addition...

As you do have 2 objects dbo. authors and user.authors with same name like authors you can't change irrespective of database owner you can't change the ownership.

There is a trick:

1....

check the credential for user 'Corporate\GeorgeW' he must be member of database role db_owner for the perticular database. Grant permission and try.

As far as I know we can't put database to comp. lev. 90 straightawy after the upgradation. You need to work on all the stored procedures in comp. lev. 90;...

Check Microsoft following website for detail:

http://msdn2.microsoft.com/en-us/library/ms143799.aspx

Thanks for the correction Minaz. It's DML trigger.

You can try DATABASE MAIL instead of SQL Mail in SQL Server 2005. I guess DATABASE MAIL is more reliable than SQL Mail.