If you're going to setup your table with a while loop, just for a set-based solution, wouldn't the direct while loop be quicker without the table? Such as :

declare...

temp tables are designed to be removed automatically when they fall out of scope.

I suggest you create a non temp table, if you wish to delete it when...

Rollouts are on Sundays but not during the first week of the month (financial company). Low-risk changes are usually on Wednesday afternoons after change control meeting.

My bad. Try:

exec SP_SOAC_REPORT_SUMMARY @FROMDT='01/01/2010',@TODT='01/02/2010'

Try:

exec SP_SOAC_REPORT_SUMMARY '@FROMDT=01/01/2010',@TODT='01/02/2010'

You could begin a transaction, update a record and then not commit until you want to end the lock.

Is there a specific question or a business problem you're trying to solve or accomplish?

So far, you haven't given anyone anything to go on. It's like saying...

Do you want us to quote you a rate?

That's as broad a question as I've ever seen here. You'll need to start with requirements.

Here's a start

DECLARE @PrincipalList TABLE (

PrincipalName nvarchar(255)

)

DECLARE @DbNumber int

SELECT @DbNumber = 1

PRINT 'DECLARE @PrincipalList TABLE (

PrincipalName nvarchar(255)

)'

WHILE @DbNumber <= 40

BEGIN

PRINT 'INSERT INTO @PrincipalList'

PRINT 'SELECT NAME FROM sqldb' +...

I'm not getting that error.

For this code, use IF...ELSE

It's a lot easier to have backups, than to explain to someone why you don't, especially during DR.

Sorry. Didn't mean to sound nostalgic 🙂

Once upon a time, developers were concerned about developing with an eye toward backward compatability and cross-platform compatability. I don't see that much anymore.

There is no way to tell.

It does for me.