Viewing 15 posts - 4,591 through 4,605 (of 22,219 total)
You can't restore to an Azure database. You can create a BACPAC and deploy that to Azure to create a new database, but a backup/restore won't work.
"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
July 18, 2016 at 9:10 am
I just recently published a blog post [/url]on this very topic. I'd suggest doing the checks that I did.
"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
July 18, 2016 at 9:07 am
I'm pretty sure you asked this question once already. Everyone suggested you use VARCHAR(MAX) but not TEXT, because TEXT is deprecated. Here's the documentation on VARCHAR. It stores up 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
July 15, 2016 at 8:45 am
GilaMonster (7/14/2016)
Grant Fritchey (7/14/2016)
Assuming those are the top 3 waits, yeah, you have page latch issues.
I'm not so sure. The average wait time is around 5ms for the SH, 1.5ms...
"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
July 14, 2016 at 7:04 am
muth_51 (7/13/2016)
"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
July 14, 2016 at 7:01 am
More information is needed. I'd double check the server configuration, memory settings, etc. Are there other processes running on that machine? What are the wait statistics? This is about investigation...
"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
July 14, 2016 at 6:59 am
Assuming those are the top 3 waits, yeah, you have page latch issues. Here is a white paper on the issue from Microsoft. Here is discussion around the issue [/url]from...
"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
July 14, 2016 at 6:45 am
wendy elizabeth (7/13/2016)
What other data type would you recommend? That is large but not as large as varchar(max) is?
I'm curious now, what are you trying to store? And which data...
"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
July 13, 2016 at 3:41 pm
Henrico Bekker (7/13/2016)
Sorry to resurrect this thread, has 2014 BPA been released? Can't find it anywhere.
No. I don't think you they are maintaining that code any more.
"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
July 13, 2016 at 11:19 am
durga.palepu (7/12/2016)
text datatype is supported in SQL 2012 but will be deprecated in future versions.alternative is to use varchar(max) and if you need multilingual support use nvarchar(max) datatype.
Thanks,
Durga
Yeah, trace is...
"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
July 13, 2016 at 7:45 am
Oh, and as far as the wait stats go, that's cumulative for the server. Looking at it in isolation for a problem of this type doesn't tell us anything at...
"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
July 13, 2016 at 6:27 am
paolobianchi (7/13/2016)
(can i find waiting cause of a single query someway? I can just profile becuse i don't have sufficient permission on server to use extended events... 🙁
Thank you!
Paolo
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
July 13, 2016 at 6:26 am
To do what you're looking for requires you to change your code to dynamic T-SQL. However, that also exposes you to SQL Injection attacks, so you'll have to write additional...
"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
July 13, 2016 at 5:34 am
paolobianchi (7/13/2016)
they seems identic to me, but ok, take the actual execution plan 🙂
Same plan, but a little bit of added detail. It's the estimate vs. actual that gets interesting...
"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
July 13, 2016 at 5:31 am
For such simple queries, there's not much in the way of tuning opportunities. The SELECT query is TRIVIAL, which means that there is only one possible execution plan. The one...
"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
July 13, 2016 at 5:27 am
Viewing 15 posts - 4,591 through 4,605 (of 22,219 total)