The only real way to automate this is with a trigger. But the trigger can be really simple and update the same table as mentioned above, then load your "backup"...

You also need to be sure that you know why the database went suspect. Check the error log for a reason.

You can clear the suspect flag as well with

sp_resetstatus <db...

While we're not really looking at doing that for a number of reasons, can you list the issues with the new forums? It's a big change for me as well,...

I use a batch file (*.cmd) that calls

isql -S ServerA -E -Q"sp_password null, new, sa" >> change.txt

with a line for each server, add a server add a line, change the...

and for the select, if the owner is "dbo" then the parser automatically resolves this. If any other user owns the object, you must query as owner.object.

Might be hidden. Is this regarding an authors area?

Try the "Jump" box at the bottom.

Sorry , never tried this. I tend to work the things separately. I know in VS.NET it is completely integrated and the debugging crosses...

What if you split this into

select @newvar =  "@intDataChangeMode=" + cast(@intDataChangeMode as char)

print @newvar

Does it still fail? I'm curious to see if you can trace one execution under MTS with...

Definitely a loophole. Here we remove public and create a group in msdb that allows package creation/editing. A separate group is used for job executions on the very rare chance...

The big thing with notification from a business point of view is that we want you to come back, so not having the text (Which is the new design) works...

http://www.microsoft.com/sql/evaluation/compare/wintercorp.asp

http://www.sysinternals.com has some good utilities to see which process holds which file open.

I agree. I might drop the transform and rebuild it. Quick and easy and usually fixes issues. Print Area can be a big one as can blank lines.

I guess you could update the table manually, but I hate to do that. I'd add the new group and drop the old one.

Not sure how you do this from VB6. You can run Profiler and see all the calls made to the SQL Server. You can also load the SP in Query...