Viewing 15 posts - 19,306 through 19,320 (of 22,219 total)
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
I like that clean up. Fewer joins and a simpler query. Nicely done.
Thanks for making me look at the query again. I've still got a bit of the debugging...
"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:22 am
That's a very good description of how to get started. If you need something a bit more fundamental, try this article on SimpleTalk[/url].
"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 5:56 am
I wouldn't recommend that either for the same reasons. Itzik Ben-Gan has a great set of example scripts that show how using NOLOCK & other dirty read mechanisms can lead...
"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 7, 2008 at 9:35 am
Easily done. You can set up a Profiler job to look exactly like what you want to monitor. Export that job to a SQL file using File, Export, Script Definition....
"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 7, 2008 at 9:05 am
From the books online:
Setting Options Without Rebuilding
By using the SET clause in the ALTER INDEX statement, you can set the following index options without rebuilding the index:
ALLOW_PAGE_LOCKS
ALLOW_ROW_LOCKS
IGNORE_DUP_KEY
These options are...
"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 7, 2008 at 9:03 am
[script]ALTER INDEX x ON z
REBUILD WITH (FILLFACTOR = 100);
[/script]
"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 7, 2008 at 8:44 am
Off hours information of system slowness?
I'm guessing that setting a trace using Profiler and getting monitoring information using Performance Monitor will do what you need.
"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 7, 2008 at 8:37 am
Viewing 15 posts - 19,306 through 19,320 (of 22,219 total)