I've located and hosted SQL Server 6.5 with documentation, see main thread post here -> http://www.sqlservercentral.com/Forums/Forum1437-1.aspx?Update=1

As usual, thanks to everyone who went out of their way to help...

Ian

Very kind - but I've managed to resolve the issues for now. It was the tempdb database filling up (pegged at 2*MB*! Not a typo!) I extended...

No, the download is duff. But vetusware.com (the abandonware site) purports to have SQL Server 6.5 in 20 .rar parts. I've downloaded it but sadly part 3 is...

Thanks everyone, I'll see if BOL is included in the download.

Just wanted to say thank you to all who replied, an interesting discussion and thanks for your positive comments.

Scowls and dark looks to the spammer, though.

Reported as spam.

I have to point out that this article wasn't about hacking SQL Server 🙂 but about using the tools at hand to gain access to databases in difficult circumstances.

Yes, the...

@richb-2 - fair point, but there's a clear difference between a locksmith and a burglar - I definitely wear a white, not black, hat.

@jeff Moden - Following on from above...

The article is a bit wordy...

1. Attempt access using DAC connection. (-m in the startup parameters). Works if BUILTIN\Administrators is a valid server login with the default...

It's updating all rows because what you are basically saying is for every row, set the bodytext equal to 'code=1' and concatenate other parameters onto it. If those other...

You probably don't need to do this since creating a non-clustered index on your final table, on the datetime column (and keeping the stats regularly updated) will allow efficient execution...

Looks like @prereplace is set to 'code1=' when other dependent @vars are null, as you're concatenating variables and a string.

So replace:

update documentbody

set bodytext = @myvar

where @prereplace is not null

with:

update documentbody

set...

I use WSH for VB scripting, i.e. I will invoke SQLCMD from a batch file, then feed it an input SQL file, then do something interesting to the output using...

The problem looks like it's the Execute As.

The login trigger proc is running as AnonLogin. Thus ANY login calling that proc qualifies as being a SPID that should be killed....

Cadavre

Thank you for your detailed reply, I've been over your code and agree that it follows the same logic. I've not been able to test it so far since...