Viewing 15 posts - 19,696 through 19,710 (of 22,219 total)
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...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 20, 2008 at 7:54 am
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.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 20, 2008 at 6:12 am
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...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 20, 2008 at 6:10 am
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.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 19, 2008 at 9:08 am
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.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 19, 2008 at 8:56 am
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...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 19, 2008 at 7:02 am
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...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 19, 2008 at 7:00 am
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...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 19, 2008 at 6:37 am
It would still help to see an execution plan.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 19, 2008 at 6:33 am
First, you don't have a where clause, so you're returing all the data from all the tables (not counting the DISTINCT statement, which, we'll get to). This will pretty much...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 19, 2008 at 6:25 am
It's probably doing a table scan, which will certainly cause a lot of reads. Are there any triggers on the table? Is that field a part of a primary or...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 19, 2008 at 6:12 am
The Books Onliine are usually part of the client install, although you can choose to not install them.
They're also available online at Microsoft:
http://msdn.microsoft.com/en-us/library/ms130214.aspx
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 19, 2008 at 6:09 am
OK. That was more helpful.
Well, for a select from the key and the key only, A would probably be faster than B. However, as soon as you decide you want...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 19, 2008 at 5:19 am
I would guess that I've seen data corruption about twice a year for... quite a while. That includes development and QA systems where silly and crazy stuff occurs just a...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 18, 2008 at 6:08 pm
I agree with Jack. You're just not going to be able to learn things in a detailed way that you don't work with daily.
That said, you should have a good...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 18, 2008 at 12:39 pm
Viewing 15 posts - 19,696 through 19,710 (of 22,219 total)