Just remember that the clustered index also stores the rest of the data with the table. You basically need to cluster on the most common access path to your data....

Just remember that the clustered index also stores the rest of the data with the table. You basically need to cluster on the most common access path to your data....

This should work:

SELECT t.TABLE_NAME

FROM INFORMATION_SCHEMA.TABLES t

WHERE t.TABLE_NAME like '%some%'

I am sorry, but I really don't understand the question.

Do you mean you have a SQL Agent Job and you don't understand why it's running slow?

True. I was assuming a stored proc. Good catch.

SQL Server comes with a built-in modeling tool. It's EXTREMELY rudimentary, but it will get the job done. You can also pick up third party tools like Embarcadero's ERStudio to...

That's a huge question. If this is the first time you're doing it, prepare to make a LOT of mistakes. First, I'd suggest picking up a really old book called...

Errors with a severity of 20 or higher stop the transaction and cause an immediate disconnect. That disconnect may be preventing the PRINT statement from occuring.

A cleaner way to...

One of the best that I know of is located here.

As to dumps from the test... This isn't hacker heaven. You should probably ask that question elsewhere.

As has already been stated, there are places where you have to use it, but, no, I don't put it around the code in my stored procedures since it does...

Great!

I use that query technique all the time. Verify that I'm getting what I want, then make it into an UPDATE statement. Glad it worked out.

Yeah, I was just going to say the same thing about the three indexes. That's what I get for doing work instead of posting to the boards.

No, it shouldn't matter that there is already data there. That's the point of the UPDATE. Did you run the query as a select? Does it return the 17k rows...

There was a session at PASS last year that showed how to make low level manipulations to the system to simulate data corruption, etc. It was pretty scary stuff, but...

If you're unsure that you're getting the results you expect from the UPDATE, then just comment out the UPDATE part of the clause and run SELECT * with the rest...