Viewing 15 posts - 7,426 through 7,440 (of 22,226 total)
A two minute restore for logs is kind of long unless you just have tons of transactions. There's no really effective ways to speed up restores. I have an article...
"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
October 7, 2014 at 4:31 am
I'm on my phone, so I can't look at the plans and this will be short.
Because we have two different servers with different memory, I would focus there....
"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
October 6, 2014 at 3:06 pm
sharadov (10/6/2014)
Here is the million dollar question!Does the query optimizer consider the load on the server when it compiles an execution plan?
No
"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
October 6, 2014 at 3:00 pm
You can just create that same schema in the next database.
"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
September 27, 2014 at 4:50 am
And roles have very little, if anything, to do with performance. They're mainly about access and availability and functionality.
"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
September 27, 2014 at 4:49 am
A checklist for database design? System maintenance? Query Tuning? Best practices for high availability? ORM implementation?
There's a lot to this job. There are no places where you can just get...
"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
September 27, 2014 at 4:46 am
Excellent point.
"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
September 26, 2014 at 4:43 am
If you want to do the second thing, you'll need to build that as a string and then execute the string.
DECLARE @ExecProc AS VARCHAR(75) --or something much bigger, depending
SET @ExecProc...
"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
September 26, 2014 at 3:51 am
You can see some long running queries in the system_health extended event session. It might show you where you had some issues. It might not, but it's something.
"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
September 26, 2014 at 3:44 am
There's nothing that Red Gate does that will capture this information. The one place I know you can get it without any changes to your system is the system_health extended...
"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
September 26, 2014 at 3:35 am
100% agreement. With few exceptions, every table should have a clustered index. Selecting that index is actually part of designing the database. The one consideration I would add on top...
"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
September 26, 2014 at 3:29 am
If you really don't want to learn extended events (and I can't think of a good reason why not) and you still want to see what queries have been 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
September 26, 2014 at 3:15 am
Phil Parkin (9/25/2014)
Grant Fritchey (9/25/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
September 25, 2014 at 9:14 am
This is exactly why you should be using source control to modify all your database objects, just as developers use it to modify code. Unless you set up auditing, and...
"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
September 25, 2014 at 8:00 am
SQLRNNR (9/25/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
September 25, 2014 at 7:40 am
Viewing 15 posts - 7,426 through 7,440 (of 22,226 total)