http://www.sqlservercentral.com/scripts/Replication/31168/

And network cable.

I've been bitten by both of those, and usually they're something I think about after a few days of pulling my hair.

Also, please edit it to the relevant part of the post you want to quote. You don't need to quote everything.

Apologies, but I don't believe I called all developers reckless. Some of this was in fun, and you might step back and realize I said...

Application logins require a password from the code (or app), and unless you can prevent the devs from knowing this, it doesn't help.

The way to handle this is not let...

Paul, nice test. I was wondering if that was a hole, and you've shown it.

I still think the best thing is to run the insert, then check for a rowcount...

The SQL Server Error log keeps getting added to as long as SQL Server runs. It restarts when the instance restarts.

sp_cycle_error_log simulates the restart process. Errorlog becomes errorlog.1, errorlog.1 becomes...

It almost sounds like a hardware issue with the new NIC.

You can't name the table and procedure the same thing.

Excellent Job, Bill!

Jamie,

I think we'd still like to know why you're doing things this way, and if you don't trust SQL Server to handle concurrency somehow.

Roy, did that blog help?

Also, where are the errors occurring? First connection, randomly while people are working? Do you get any errors from the local connections like from Agent?

If this is a regular problem, you need to buy more space. It's that simple.

Mapping shared drives will work...sometimes. However it likely will fail when your database fails, and then...

Michael Lysons (5/8/2009)

---

Good grief, sweeping generalisation about developers there, Steve. Seems to me that if a developer is implementing incorrect indexes etc, then it's actually the DBAs fault for...

Blinkering?!?! Blimey, major, Great Scott, you bloody well confused me!