Thats the classic way of migrating to another server and minimizing downtime and will work well for you.

Those databases that are only 20MB probably not worth it though. Full backup...

I would suggest changing the DELETE statement to commit in smaller batches and let the trigger take care of itself.

the TOTAL table does not contain a column job_title

offline

alter database

online

has the advantage of not changing the database owner or possibly ending up with a different dbid which can throw off default database settings.

this is probably a parallel query.

see if only one connection shows as runnable with the others suspended. A waittype of CXPACKET would confirm it.

did you move or copy the files?

to tell SQL the files have been moved use the alter database command

alter database dbname modify file (name =, filename =' ')

I would expect...

in a nutshell for a datafile it shuffles all the extents to the front of the file. It does not care how it...

restore from backup!

Bhuvnesh (5/5/2010)

http://msdn.microsoft.com/en-us/library/ms177484.aspx

or see BOL

sounds like you installed just the management gui and not the database engine itself:

http://www.microsoft.com/express/database/

I think we agree david that the important point is that the non-clustered index be covering.

thanks for sharing.

but of course you now have an index that offers no performance gain on selects but will need to be maintained on updates/inserts and double(?) the space used...

On a table with a clustered index the clustered index key is already contained...

If you are logged on as 'sa' at the time you do the initial restore of the logshipped database with the norecovery option, the database will be owned by 'sa'.

Once...

restore filelistonly holds that info