Is the query complex? Got enough room in tempdb? Updated statistics?

Andy

http://www.sqlservercentral.com/columnists/awarren/

The error logs? If they are large it can take a long time to pull them across, better to copy the file down locally and open with NotePad.

Andy

http://www.sqlservercentral.com/columnists/awarren/

Agree.

Andy

http://www.sqlservercentral.com/columnists/awarren/

The file size will only get smaller if you do a shrink on it. Typically you want to set the file size large enough to handle the largest transaction you...

Its a server that has the service stopped. Could some people try the test code I posted earlier?

Andy

http://www.sqlservercentral.com/columnists/awarren/

I dont think so. Usually better to do an explicit create of the table anywhere and that would let you set the filegroup.

Andy

http://www.sqlservercentral.com/columnists/awarren/

Related to jobs on target servers maybe?

Andy

http://www.sqlservercentral.com/columnists/awarren/

Bill, you should just be able to install SQL2K as the default instance and it will upgrade the files automatically. I don't remember trying to move master using the technique...

Not being able to open the default db makes sense, since it is probably the one missing. I always leave all of mine set to master just for simplicity, never...

Interesting. Did you select the force restore over existing db option? Thats the only thing I've thought of that would cause your previous db to disappear. Regardless of what happened...

Bak is a convention, not enforced. So the backup was successful but you had problems restoring? Did you do this from Enterprise Manager? A list of steps taken so far...

Never needed it much so far! I ran this as a test:

Dim oserver As SQLDMO.SQLServer

Dim sngStart As Single

On Error GoTo Handler

Set oserver = New SQLDMO.SQLServer

With oserver

.LoginSecure...

Not sure what happened. Usually backups go to xxx.bak file, totally separate from the mdf/ldf. Did you do a sql backup? Or stop the service and make copies of the...

Possibly you can do it like this, I dont have a machine handy with the SQL7 dmo dll's on it:

Set oapp = New SQLDMO.Application

Debug.Print oapp.VersionMajor & "." & oapp.VersionMinor

If that...

Generally you don't want nested triggers enabled. Just wasnt sure if maybe that was why the triggers were firing multiple times as you mentioned. Triggers fire once per transaction -...