Sorry no. Fortunately mine haven't gone wrong yet. But i tried it one of my dev boxes and

RESTORE DATABASE mytestdb WITH RECOVERY

worked fine on my mirror partner as it...

Oops I meant 2005 just my typing again

David

Just run restore with recovery against the database that will bring it online and then you can drop it.

David

In 2004 you query sys.sql_modules

David

For the server 2005 stuff you should look at the performnace dashboard reports that came out with sp2. Oh and they do only work with sp2.

http://www.microsoft.com/downloads/details.aspx?FamilyId=1D3A4A0D-7E0C-4730-8204-E419218C1EFC&displaylang=en

and there is a...

You're correct a full database backup will not truncate the log you do have to run a seperate transaction log backup to so this.

David

Erik

At the moment your trigger will fire whenever any column is updated so I would modify your trigger in one of two ways depending on how you update your table....

Thats quite interesting David I had never though of using CASE like that in the where clause of a query.

David

I am very sure that you cannot use the CASE function in the where clause of a query

Why do you not work this out using conditional logic before the query...

Yup you can detach and attach to your hearts content.

David

It is also recommmended to run dbcc checkdb with data_purity on each database immediately after you upgrade.

You should also remember to update the statitsics on your databases afetr the upgrade...

There's good article by Erland Sommarskog on this where he compares all the different methods for doing this

http://www.sommarskog.se/arrays-in-sql-2005.html#iterative

David

CREATE SCHEMA myviews with authorization dbo;

CREATE VIEW dbo.nastyview

AS .....

ALTER schema myviews TRANSFER dbo.nastyview

David

These two threads may help you

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1269577&SiteID=1

http://support.microsoft.com/default.aspx/kb/929772

hth

David

There's a nice wee article here

http://blogs.msdn.com/psssql/archive/2007/04/06/post-sql-server-2005-service-pack-2-sp2-fixes-explained.aspx

which explains the mess theat is SP2.

hth

David