did you log grow over night to 17 Gb ?

or is it due to the fact you do not make log-backups ?

In full recovery mode, you need to make log-backups...

you should be able to update directly to SP3.

There is a CU1 for sp3, but you'll have to check it the items fixed would match your usage environment.

Indeed, a word of caution should be said.

Undocumented surely means the behaviour may change with every hotfix/cumulative update/service pack/new version.

They may even be removed without any notification or alternative !

Thank you for the confirmation 🙂

There are some more special characters you need to double up when using them in T-sql or in a dynamic sql string.

If you use variables from you calling application (vb.net,..)...

Books online has good info.

"create event notivication" and further...

Be sure to use the most recent one (dec.2008)

- figure out how many times the application calls the sproc in a single application run. (or how many times it executes the cmd-object)

it must be a loop of some...

Best is to run your code on a box where you have a sql2005 client installed.

If you need to run the code locally on a box, best is you...

Nicholas Cain (1/10/2009)

---

If you had mentioned that this was only an issue through the app and not when run manually, which was what everybody thought, this could have been resolved...

SQL Noob (1/9/2009)

---

we put it in QA on a server with SP2 and no CU's. In a week or so we are putting it on a QA server with SP2...

Like Gail said, because it is a big sproc, with multiple functionallities, it may be hard to "just optimize by reading it" and therefor it is better to split it...

- an update trigger is fired by an update event at object level (table/view) !

(so not only from your sprocs, but also by all other update statements !)

- one...

- loose the dynamic sql ( http://www.sommarskog.se/dynamic_sql.html )

- why are you using the hints with the delete statements you are executing ??

- don't comment (--) lines in your...

Mark (1/9/2009)

---

I...

ALTER PROCEDURE [dbo].[sp_UpdatePlays]

-- Add the parameters for the stored procedure here

@username varchar(50)

AS

BEGIN

-- SET NOCOUNT ON added to prevent extra result sets from

-- interfering with SELECT statements.

SET NOCOUNT ON;

...

with regards to locking, in many cases this is not a good solution.

If you want to be ablosutely sure you don't update...