Viewing 15 posts - 6,511 through 6,525 (of 22,229 total)
I'm with Kevin. And the way around this is to try out the third party software on your own. Don't look to them for support. Test it and see 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
March 31, 2015 at 12:06 pm
I'd suggest looking at the statistics in more detail, especially on the tables that are the biggest or that are called the most frequently. Get a sense of how the...
"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 31, 2015 at 12:03 pm
Steve Jones - SSC Editor (3/31/2015)
Grant Fritchey (3/31/2015)
I use semicolons on terminators for all my statements. Everyone should.
You do or Prompt does it for you?
Well, Prompt does it for 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
March 31, 2015 at 11:18 am
stephen.long.1 (3/31/2015)
Regardless of the merits of adding semicolons at the end of all statements (something which I don't do, but...
"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 31, 2015 at 8:10 am
Just not crazy about this phrasing:
Since few semicolons are used,
I use semicolons on terminators for all my statements. Everyone should.
"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 31, 2015 at 7:08 am
And when you think you have a handle on the changes suggested, all good, take a look at the execution plan to understand how the optimizer is resolving the query....
"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 31, 2015 at 7:06 am
What you can do is restore your database to another location and then run the full CHECKDB statement there. You really do need to do the internal logical checks as...
"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 31, 2015 at 7:04 am
You may just have a long running transaction. Check to see if that process is blocked by looking at sys.dm_exec_requests.
"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 31, 2015 at 7:02 am
This is the reason you're taking full backups and log backups. Restore to a point in time prior to the corruption of the 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
March 31, 2015 at 7:01 am
GilaMonster (3/31/2015)
spaghettidba (3/31/2015)
GilaMonster (3/31/2015)
Not efficient as it prevents index seeks, not that a text column can have indexes, but I don't like teaching bad options.
Exactly my point: a bad option...
"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 31, 2015 at 6:57 am
jellybean (3/31/2015)
Process to up-greade to SQL Server 2014 from 2005
0. On the *separate* target box install Sql Server...
"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 31, 2015 at 6:55 am
Jeff Moden (3/30/2015)
krypto69 (3/30/2015)
Long story, but it's financial data and I'm new there so can't complain..yet.
Kinda figured those were my only options. Shame I can't use my high avail...without...
"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 30, 2015 at 7:35 pm
You'll have to combine that view with other functions and views to get a complete picture. You can use sys.dm_exec_sql_text to get the query and sys.dm_exec_query_plan to get the plan.
I'd...
"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 30, 2015 at 6:57 pm
Why would developers need live data to develop against?
But, if you have to, the technologies you have available are somewhat limited because they will prevent changes to the database. For...
"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 30, 2015 at 3:06 pm
The best way is to capture queries using extended events. You can see how much memory the query consumes. You can also look at sys.dm_exec_query_stats to see some aggregation information...
"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 30, 2015 at 3:02 pm
Viewing 15 posts - 6,511 through 6,525 (of 22,229 total)