The single biggest thing I would do is allow the option to select not only which distributor to use, but which distribution database. Replication shouldn't be bound at a server/server...

The reason you're getting the "No Column Name" error is because you're using temp tables. SSIS can't read metadata from your statement due to this issue.

My workaround is instead of...

Bingo:

SELECT * FROM sys.fn_get_audit_file ('\\serverName\Audit\HIPPA_AUDIT.sqlaudit',default,default);

Probably compressed XML... Raw XML is fairly readable while the SQAudit files have all those whanky chars in them.

Thanks for the info.. How strange that MS would provide this file but no real automated ETL process to extract the information... (At least not to my knowledge yet...)

I don;t really have an answer but I am also curious about your question. I'm just getting auditing set up myself.

My question I think will be about how to...

..and be VERY CAREFUL with those Login triggers. I once accidentally locked everyone (Including SA :Whistling:) out of a critical server because of an errant Login trigger configuration. Brush up...

Let's see if this works....

Please note: I am not the original author. Some talented individual wrote this for SQL 2000. In it's original form it didn't work in 2005...

I purposely chose the over-budget method because no matter how you slice it, if you take shortcuts in building out an environment... sooner or later (Usually sooner) you will be...

...but if you are creating a stored procedure and using a command that will be phased out in future versions (DBCC INDEXDEFRAG), you'll have to go back and edit that...