I agree, nice re-write, Paul.

You need the log space. The only thing that will let you use less peak log space is more frequent log backups.

Fair enough, Paul White. I'm not sure what I could do here now other than watch for more info and revise things when it's available.

If it's not clear to you,...

sys.sql_logins

http://msdn.microsoft.com/en-us/library/ms174355(SQL.90).aspx

There must be something else, like what Gail has listed.

I think some products use .dat as an extension. Someone may just use that as a default, which is a bad idea.

I pinged the ZDNet writer. He is looking into it and will likely post an update.

and this works?

There must be something in that connection / session that creates #con.

AFAIK, an explicit create or select..into is needed.

OK, heard from Andy. Didn't get any props. He thought he'd get a few things, but his budget was blown in 17 seconds, so he stopped bidding.

No assumptions, bitbucket, on the success or failure of a project. This is at a lower level of where developers make mistake in the coding, not in interpreting the requirements...

John, feel free to rebut with your own article. We can link the two together.

You can check here: http://www.sqlauthority.com

Please write out your question and be polite. I think this is a legitimate question to give you guidance.

And we solve it.

hey, just hire a monkey, give him a macro that gets to the forums here 🙂

There will be things that apply from that book. David Litchfield is an extremely well respected security expert.

I'd also look at these two:

How to Cheat at Securing SQL Server 2005

SQL...