Viewing 15 posts - 8,371 through 8,385 (of 22,226 total)
andrew gothard (4/22/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
April 22, 2014 at 6:22 am
SQL Swerver (4/22/2014)
GrantHow can the WASD Firewall be configured to allow Azure Weblications? They are internal to Azure with no external IP?
All the cloud services that I currently have (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
April 22, 2014 at 4:42 am
SQL Swerver (4/22/2014)
How would one configure the Azure SQL Database firewall to allow an Application hosted in Azure PaaS...
"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
April 22, 2014 at 4:39 am
Use correct data types. If you need a floating point number, use a float. If you're expecting an integer, use one of the integer data types, not the float.
"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
April 22, 2014 at 4:20 am
I'm with Yogeshwar Phull. Don't use show_contig any more. The dynamic management objects are so much better for this type of 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
April 22, 2014 at 4:20 am
Deadlocks are fundamentally a performance issue. So, are the other databases the same size as the one that's getting the issue? Are the same indexes in place? Are the statistics...
"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
April 22, 2014 at 4:18 am
Here's the Books Online entry on DDL Triggers.
"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
April 22, 2014 at 4:13 am
The thing I'd look to are the wait statistics. What's causing the system to slow down? That will tell you if you are stuck on I/O or if 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
April 22, 2014 at 4:12 am
I'm pretty sure there's no way to trace by JobId. But, you can trace by application name, so that will make it so you only ever get calls from 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
April 21, 2014 at 4:21 pm
You can get a bunch of information from the backup files themselves, all through T-SQL. I've got an article on it over at Simple-Talk[/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
April 21, 2014 at 4:14 pm
Steve has largely nailed it. Be cautious using extended events to capture all statements though. That can be a ton of information.
Now, if you're running SQL Server 2014, you can...
"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
April 21, 2014 at 10:29 am
Probably a double hop on Kerberos and I was going to link to the same article. That's the place to go.
"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
April 21, 2014 at 10:23 am
Again, for PDW, I strongly advise you track down information from PragmaticWorks. They're the experts. Here's their web site.[/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
April 18, 2014 at 3:34 pm
Yeah, I've applied to Maine, but no word on if I got picked. I'm doing a pre-con at Albany, so I'm pretty sure I'm picked there. See you at 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
April 18, 2014 at 3:32 pm
In general, I would consider this a very dangerous position. You may have dirty data in your systems and you won't know it.
Now, you may be in one 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
April 18, 2014 at 12:37 pm
Viewing 15 posts - 8,371 through 8,385 (of 22,226 total)