Viewing 15 posts - 9,136 through 9,150 (of 22,232 total)
I would change it immediately after installing SQL Server. The default value is just ridiculously low.
"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
January 6, 2014 at 10:31 pm
Good answer, but that's not even "from SSMS" That's Agent using PowerShell. There's no way I know of through SSMS directly. You'd have to do some command line magic of...
"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
January 6, 2014 at 9:04 am
No, it's not a good idea to change it at the server level. Most of the time you get parallelism on queries that are not complex enough to justify it....
"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
January 6, 2014 at 9:00 am
Oh, nice catch, I didn't see that.
Still look at the execution plan. It's a foundational start to everything you do when trying to tune performance problems on queries.
However, I'm still...
"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
January 6, 2014 at 5:23 am
Ed Wagner (1/6/2014)
GilaMonster (1/6/2014)
Ok, who has the crystal ball this week?http://www.sqlservercentral.com/Forums/Topic1527890-146-1.aspx
http://www.sqlservercentral.com/Forums/Topic1528036-391-1.aspx
I think I'd have to vote for the 270-column table where the upload is not working properly. It made me...
"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
January 6, 2014 at 5:21 am
All you did by detaching the database was flush queries out of the cache (and probably flushed data out of the cache too). That's not a solution. Instead, 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
January 6, 2014 at 5:18 am
It could be process, your server set-up or your code. Most of the time, it's the code. I've got a book on SQL query tuning that walks you through gathering...
"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
January 6, 2014 at 5:15 am
Ed Wagner (1/6/2014)
"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
January 6, 2014 at 5:13 am
The code looks to me like it will be likely to use that index. Have you checked the execution plan to see what it is doing?
"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
January 6, 2014 at 4:19 am
What changed on the machine? It's unlikely that the server instance just suddenly decided to stop working. Surely something lead to the initial problem. I'd look there to figure 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
January 6, 2014 at 3:48 am
If the process you're currently using has a command line, try using PowerShell. You can fire a powershell command right from SQL Agent.
"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
January 5, 2014 at 2:09 pm
Not a problem.
Just so you know, I cheated in figuring out what was up. I used Red Gate SQL Prompt. It's a software my company makes. It's invaluable when working...
"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
January 4, 2014 at 1:02 pm
You were missing a parenthesis after the first date operation. You don't need all those parentheses. You can have it just like this:
SELECT [displaydate],
...
"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
January 4, 2014 at 12:41 pm
The first query is an old style ANSI 89 syntax join with the join criteria in the WHERE clause. The second is a modern style join with the join criteria...
"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
January 4, 2014 at 4:00 am
Since you know the specific query, your job got easier. You want to look at the code to ensure it's not using functions on columns in the WHERE clause 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
January 4, 2014 at 3:50 am
Viewing 15 posts - 9,136 through 9,150 (of 22,232 total)