If "most" of your queries require DISTINCT or GROUP BY to eliminate duplicates then, in general terms, you're writing your queries incorrectly or the data design is wrong. While there...

I have to agree. 2 is fine. 1 & 3 are silly limitations. If you're going with pure natural keys, maybe then you never use identity, but if you're just...

Instead of using the sub-query as part of the select list, make it a derived table, join against it, and you'll get a row for each value in that table.

We're using them all over the place. It allows us to set up different security management processes within the same database and maintain them very easily since you can grant...

No, nobody should beat you up. "It depends" is always the right answer. The factors involved really do make a difference. If the system in question is meant to gather...

Everyone else has already said it, but I can expand a bit. XML is the answer. You want to look at ALL your database processes from the approach of working...

DonaldW (4/10/2008)

---

Grant Fritchey (4/9/2008)

---

Our starter questions are:

What's the difference between a clustered & non-clustered index?

What's the difference between blocking & deadlocking?

How do you trap errors in SQL Server 2005?

What does...

Our entire enterprise is running on TCP/IP connections (I suspect most are these days). If you can connect to your SQL Server instance and run 'SELECT * FROM SomeTable', then...

It's possible that it could be as problematic as anything else, but you might try dropping & recreating the index. That will also remove fragmentation. The Storage Engine team at...

Sounds like heaven. We're trying to convince our bosses to let us telecommute regularly (we're able to do it now on snow days or when the cable company is coming...

Sorry, it was joke. Jeff asked how to...

We've found the fastest way is to export from one database out to an SSIS RAW file and then back into the next database in the next server. Storing the...

Because we use DBPro (aka DataDude) I do a lot of TSQL programming in Visual Studio. It's not terribly good, but the integration with TFS & DBPro makes it necessary.

You will have to pass them in for a SQL guide.

Here's an example:

EXEC sp_create_plan_guide @name = N'APlanGuide',

@stmt = N'SELECT * FROM [Person].[Address] WHERE [City] = @0',...

You call out of TSQL to WMI process to launch a .NET app... right?