For this volume of data I'd suggest good old fashioned bcp to extract the data using the -F (first row) and -L (last row) execution flags. Also since you are...

Try China instead. You can get 30% resources for the same cost !

Out of my 22+ SQL Servers the smallest tempdb is 1024 Mb data/512 Mb. both data and log have 'autogrow' by Mb with limits. The growth factors are 512 Mb data/256 Mb...

For starters, you are executing the RTM version (original CD installation, with no service packs). Upgrading to SP4 may or may not be advisable. You defintely want to search this...

We use RDP exclusively. Whether in the office or out of the office. Our only trips to the server room are for vendors, hardware installations/upgrades ans SAN maintenance/upgrades. The only...

It seems from a performance thresh hold perspective Phil's information is of more value. Our RS database is less than 2 Gb. We only run 'on demand' reports for MOM...

Do any of your table names have embedded spaces in them ? This could cause a parsing error.

For performance try executing 3 batches of 31 tables concurrently ... or something...

You might just want to hang this one up. MS just announced yesterday (09/15/2005) that 'mirroring' in SQL 2K5 is not ready for release. You can turn it on with...

I am going to assume that the database was backed up using the 'ArcServe agent'. If this is the case then your database may not be usable. I've tested various...

If you are not using replicatino simply delete the files from thier locations. If you decide to use replication later, then the databases will be created for you (and you...

So long as select still works I'll use it (even though set is less to type !). The one advantage is the ability to set multiple values. The most obvious...

has anyone modified the settings on the SMTP server ? I know at our location we only allow specific IP addressess to 'forward' things toi the SMTP server. If you...

One easier function than COALESCE ... it more closely mimics the structure of your MySql  statement (and provides the same functionality).

But be wary of the 'management credo' --> "If it ain't broke, don't fix it". Also, fi you are using 3rd party applications you'll need to check them as well...

I order to minimize the impact each has on the other (if they must co-exist on the same server) I'd fix min/max memory on SQL Server and also limit memory...