kkapferer (11/6/2009)

---

Thank you all for your suggestions. A more senior DBA here advised me that I was overthinking this problem. He suggested I just delete the user...

A practice that comes in handy:

When doing any sort of manual update in a production database, wrap it in a transaction, and don't commit till you know the results will...

It mainly depends on what you want to accomplish with your audit log.

You could use a transaction log parser. Database needs to be in full recovery (should be anyway...

No. You would do this through either Windows built-in backup, or through whatever backup software you're using for everything except databases. Regular file backup.

http://www.microsoft.com/downloads/details.aspx?FamilyID=000364db-5e8b-44a8-b9be-ca44d18b059b&displaylang=en

I've never seen having two case statements in a query make a difference in its performance vs one case statement.

I have seen lots of places where UDFs kill performance. ...

Open the package in Business Intelligence Development Studio. Should be in the same directory on the Start menu as Management Studio is.

Creating the databases with the views is going to be easier than creating the necessary dynamic SQL statements, in the long run.

You wouldn't use the exec command for the select...

Parsing just checks syntax. Compiling checks for objects.

Dynamic SQL is the only other way I know of, like my first example.

Batch complete

My suggestion is build a DBA database on each server, and have a view on it that pulls the columns you need in the format you need from the table...

Run a backup on the directory the log files are stored in. That's the easiest solution. If it's a diff backup, you'll only get files that have changed...

The only way to do this is with dynamic SQL.

if 1=3

exec('select [Job_id], [name], [freq_interval] from msdb..sysjobschedules where freq_type = 8');

Of course, that raises the question of why you'd want to...

Try it and see. That's the best way to really know it.