Viewing 15 posts - 19,306 through 19,320 (of 22,226 total)
If anyone has a volume 4 laying around, I'd love to get a copy.
"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
November 16, 2008 at 3:54 am
That's odd. There used to be a link to buy them. I can't find it anywhere. Steve!
"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
November 14, 2008 at 11:36 am
Last time I tried, the files were locked. You can set up a rollover so that you're getting a new file every so often and the old files are available.
Alternately,...
"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
November 13, 2008 at 6:33 am
It's also possible that you have different default ANSI settings on the two machines. This could affect performance. A good way to test both would be to use a trace...
"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
November 12, 2008 at 7:37 am
The first response pointed out a number of issues you have'nt talked about addressing. Query tuning, indexing and all the associated work around those issues can and do lead 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
November 12, 2008 at 7:02 am
I understand why you might not build constraints in a data warehouse (sort of), but it makes no sense at all to choose not to build indexes. I mean, you...
"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
November 12, 2008 at 6:59 am
Check this article 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
November 12, 2008 at 6:53 am
Do you mean when you connect to a server from your machine the query takes longer than when you run it directly on the server? Data travelling across the network.
If...
"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
November 12, 2008 at 6:44 am
I think you might be better off with an index on these columns: box_no , msisdn, log_time. Then you'd have a covering index. The reason it's not using the index...
"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
November 11, 2008 at 6:16 am
Do you ever do a FULL SCAN on the statistics or just rely on the default behavior? The thing is, rebuilding the index on Friday updates the statistics. Running another...
"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
November 11, 2008 at 6:10 am
It's even possible that the index is actually not selective enough for the optimizer to choose it for the query. Even though you're forcing it's use makes the query run...
"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
November 10, 2008 at 8:45 am
Not unless I've missed it to. If the value of a number is -3, it's -3, not 3 with some negative sign kept elsewhere that may or may not change...
"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
November 10, 2008 at 6:59 am
Just a vote. 1,2,4, yes because I've done them.
3. I'm not sure, but I lean towards no. I guess it depends on how you create the report. I'm just not...
"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
November 10, 2008 at 6:56 am
Here is an entry in the Books Online (SQL Server documentation) that should get you started. It includes sample code.
http://msdn.microsoft.com/en-us/library/aa225983(SQL.80).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
November 10, 2008 at 6:49 am
You don't really have any options in SQL Server 2000. The best you can do is check after each statement for an error value and use a GO TO 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
November 10, 2008 at 6:44 am
Viewing 15 posts - 19,306 through 19,320 (of 22,226 total)