Job postings such as this would generate a lot more interest, potentially, if there was a suggested starting salary.  Unless the potential employer is cheap, in which case, they shouldn't...

SQL Server will, by design, use up gobs of RAM -- as much as it can get.  It should free up resources if other apps need it.  I wouldn't dwell...

It should be possible to create the MySQL box as a linked server, then use normal queries to MySQL to get the data you need.  I'd be curious to see...

I prefer VB, but you'll find more sample code in C#.

There was a great script here just recently, sp_grep, which allowed you to search your stored procedures.

The publisher has to know that the subscriber has been updated.  The first message is probably that verification of transaction being recorded in the publisher (in the distribution DB?)

Maybe someone...

There are a few utilities which will let you view the transaction logs.  You would be able to find the change, and see the previous values using that.  There are...

I agree with the no reboot policy.  My production server runs for months with no attention or reboots.  Server 2003 and SQL 2K are rock solid.

Especially look at the "Quoted Identifier" setting for your stored procedure.  The column names such as "free" may be causing the error.

My guess would be that the sp_executesql wraps the code in a transaction, while the SQL run in QA is not.

Not pointed out is the fact that a stored procedure is optimized once, then reused from the cache.  A SQL query may be optimized to be as fast as a...

I can't see any reason why you shouldn't delete the table, then run the integrity check on the DB.  I wouldn't bother trying to repair a table you are deleting.

I use the TRUNCATE option after the weekly maintenance tasks are run, because I don't care about the 2 GB of log entries that record the reindexing etc.  This happens...

Don't forget to update the SQL Agent account, too.  That is what runs the jobs.  Also, there is an 'owner' entry in each job that you may want to double-check.

Triggers are the best way to do that, unless you can rewrite the application(s) to record changes.  If you *need* to record changes, why are you worried about a performance hit? ...