Mike nailed it pretty well. I can't add much.

But I'll say this. Imagine a piece of TSQL code that, let's say, inserts data into three tables. You can put a...

That's a huge topic. I have a chapter in a book I'm writing for Red Gate waiting for tech edits on this exact topic right now.

There are any number...

Copy the data between the databases using... replication or triggers or whatever. Then you only have to give your users access to the database they're supposed to have.

Because there is no data in the temp table when it gets created, there are no stats. Without stats, you get an estimate of 1. You can update the stats...

First, you have define exactly what you mean by auditing. There are different levels of requirements depending on the laws or regulations or business or technical needs that you're attempting...

You can't view the transaction log file, at all, unless you purchase a third party product specifically made for reading the log.

Why do you need to do this? You should...

ASsuming I understand what you're asking, you want to have a single query that will hit the appropriate schema depending on the user that is making the request? The only...

Instead of a group by clause, I'd suggest going with either an ORDER BY and select the TOP 1 value or use the OVER ORDER BY with the ROW_NUMBER in...

Best tool I know of for working with models is Embarcadero ERStudio.

But if you do a search, there are free ones out there, but you're going to get what you...

Richard M. (5/17/2010)

---

James Stover (5/13/2010)

---

I stopped being helpful online about 5 years ago. I'm not interested in helping some stranger in the far reaches of <insert developing nation here> to...

To know if servers are down, you need to enlist yet another server as the monitoring point, pinging the original servers to see if they're alive.

The thing is @@ERROR really doesn't catch errors, it reports them. TRY/CATCH can literally catch, say, a deadlock, and let you retry the query. That difference alone is a great...

Since you're doing updates, you do have to worry about two searches there, the search within the table for the correct records to update and the select statement & join...

There must be differences, index fragmentation, statistics age, contention for resources, available memory, connection settings, lots of these things can cause differences in performance.

Basically if the error will cause a disconnect, SQL Server can't catch or handle the error, so the calling code will have to.