Viewing 15 posts - 5,011 through 5,025 (of 22,221 total)
Not enough to go on. What do the wait statistics look like? What is causing the server to run slow. Is it slower than another server? What are the differences...
"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 8, 2016 at 10:04 am
SQL!$@w$0ME (3/8/2016)
Thanks. Any possibility of using the existing on-premise AD accounts in azure db?
It has to be through a hybrid environment, but yes. It's in preview right now[/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
March 8, 2016 at 9:33 am
Isn't the official time 3AM when it changes, but yeah, you'll lose an hour.
"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 8, 2016 at 7:35 am
I don't know of a sure way to speed that up. We used to do the same thing in this order:
1. Restore production backup to a staging server
2. Clean 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 8, 2016 at 7:21 am
If you are moving towards a hybrid system with AD inside of Azure, I would pursue that. If all the access is directly from Azure, then you get a choice...
"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 8, 2016 at 7:14 am
A good practice to get into is setting all the server dates and times to UTC and then working with data offsets from there. You'll get much more consistent behavior...
"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 8, 2016 at 7:12 am
Performance gains on a clustered index are mostly going to come when that index is used to retrieve the data. While the approach of putting a cluster on the primary...
"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 8, 2016 at 7:10 am
Jeff Moden (3/7/2016)
Grant Fritchey (3/7/2016)
The main thing is that there are no additional trace events being added.BWAAA-HAAAA-HAAA!!!! That means that it's finally stable! 😀
Ha! Right. Like SQL...
"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 8, 2016 at 6:09 am
There is absolutely no hard and fast rule "Do this and you'll be fine." Picking and choosing indexes is extremely dependent on the workload in question. Foreign keys are good...
"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 8, 2016 at 5:45 am
Jeff Moden (3/7/2016)
Grant Fritchey (3/7/2016)
You shouldn't be using Profiler anyway. Instead, use extended events.
Heh... I strongly agree... to disagree. 😛 Maybe it's just the bad taste in my...
"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 7, 2016 at 8:23 am
You shouldn't be using Profiler anyway. Instead, use extended events.
The other posters largely have it right. I'm just piling on.
First, you have to identify what is causing stuff 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
March 7, 2016 at 6:06 am
It's got to be due to the version.
"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 4, 2016 at 4:34 pm
But, what version is the SSMS tool that you're using on both?
"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 4, 2016 at 2:24 pm
jasona.work (3/4/2016)
WayneS (3/4/2016)
jasona.work (3/4/2016)
To anyone who has gone on any of the previous SQL Cruises, if you brought...
"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 4, 2016 at 8:55 am
And then the last statement is usually RESTORE ... WITH RECOVERY so that the process concludes.
"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 4, 2016 at 8:45 am
Viewing 15 posts - 5,011 through 5,025 (of 22,221 total)