Viewing 15 posts - 17,926 through 17,940 (of 22,219 total)
Not without some structures and execution plans. It's just too hard to guess at what might work in your circumstances.
"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
March 26, 2009 at 5:46 am
Actually, it works fine. I just did it. You get the query results and the messages in a single window when you change the output from the default grid 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
March 26, 2009 at 5:44 am
I'd suggest picking up a copy of Craig Mullins book "Database Administration." It's technology agnostic and just talks about the job of being a DBA. It's a great read.
"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
March 26, 2009 at 5:33 am
One option is to change the output of the results from a grid to text. Then the columns and the I/O all come out in a single window.
"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
March 26, 2009 at 5:31 am
You should look up full text indexing for the varchar(max) column. That's the best mechanism for use with this sort of thing.
Are there other indexes on the table? A PK?
"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
March 26, 2009 at 5:30 am
As Flo says, you shouldn't have to rebuild the index right after creating it.
Are you sure the index is working well with the query? Did the execution plan change before...
"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
March 26, 2009 at 5:25 am
The truncate_only operation has been deprecated in SQL Server 2008. There is no replacement. The log is automatically truncated when the db is in simple recovery. There are more details...
"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
March 26, 2009 at 5:22 am
This may not give you the answer, but it could help. Get the estimated execution plan instead of the actual one. I usually prefer to work only with the actual...
"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
March 25, 2009 at 6:00 pm
Yep. A Star Fury from B-5.
"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
March 25, 2009 at 5:22 pm
I think I lost all the posts from this morning. That stinks. I wrote a couple of decent ones (for once). Ah well, no joy in Mudville.
"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
March 25, 2009 at 4:46 pm
From conversations I've had with people who were on the committee, the DBA track has the fiercest competition. Since you're on that track... it'll be tough. But you know what,...
"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
March 25, 2009 at 4:24 pm
So, it looks clear now?
"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
March 25, 2009 at 10:15 am
GilaMonster (3/25/2009)
RBarryYoung (3/25/2009)
You know I am not getting my email alerts/updates this morning either. Something is definitely off.
Likewise. I've had one notification since about 9am this morning (GMT+2).
I...
"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
March 25, 2009 at 9:39 am
RBarryYoung (3/25/2009)
I tried deleting the duplicates, but I don't think that...
"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
March 25, 2009 at 9:37 am
The basic code doesn't cause locking all by itself. So, the problem must lie elsewhere. Are you getting errors? Does the code that's calling the proc have a transcation wrapper?
"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
March 25, 2009 at 7:25 am
Viewing 15 posts - 17,926 through 17,940 (of 22,219 total)