Well, for sqlserver < ss2005 "specific_schema" = "owner"

If you don't want to filter based on owner, just comment the where clause.

you can run...

Are u allowed to use regedit ?

check [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\yourdsn

and remove the "Database"="faultydbname"

or replace it with a correct dbname

or remove the full...

how about :

-- grant select, insert, update, delete

DECLARE @SQLStatement nvarchar(4000)

DECLARE csrGrants CURSOR LOCAL FAST_FORWARD READ_ONLY  FOR

 Select  'Grant select, insert, update, delete on [' + [TABLE_SCHEMA] + '].[' + [TABLE_NAME] +...

can you remove the odbc-dsn  and then build it up again ?

Offcourse you'll have to check execution plans, but the optimizor will see trough it (I hope)

This would result in a query like this...

Nope

- take a look at SQLDMO

- maybe this can help you out ...

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=23&messageid=107508

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q220/1/63.asp&NoWebContent=1

"C:\Program Files\Microsoft SQL Server\MSSQL\Upgrade\scptxfr.exe" /s yourserver /d...

did someone drop and recreate the database ?

Connect using Query Analyser. You'll also get the message, but it will connect to master and you can work from there on.

There must be a reason they put the trigger overthere !

If you're not sure, don't disable it !