Viewing 15 posts - 4,876 through 4,890 (of 22,224 total)
My experience with this is about 6 or 7 years in the past. I remember getting the issue and how we solved it. That's about it. Sorry.
"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 6, 2016 at 6:52 am
It is VM vs. Hardware, which can't be discounted. Just because the resource settings in the VM are the same as the hardware doesn't mean they're actually the same. 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
April 6, 2016 at 5:58 am
As a part of your development process, I strongly recommend you get your database into source control. This gives you the ability to track changes and, quite importantly, easily recover...
"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 6, 2016 at 5:55 am
Also worth pointing out, with connection sharing, you may see a single connection that's been on for hours, but it's actually been used by a large number of people over...
"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 6, 2016 at 5:52 am
There's no need for this. What problem are you trying to solve?
"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 6, 2016 at 3:06 am
Upgrading to 2014 or 2016 is basically an identical amount of labor. With that in mind, I'd go for 2016. Yeah, it's newer, it might be a little rocky in...
"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 5, 2016 at 12:57 pm
Also, fair warning, if you encrypt a file, it won't compress well. Good backup software compresses, then encrypts.
"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 5, 2016 at 11:47 am
SQLRNNR (4/5/2016)
Grant Fritchey (4/5/2016)
Phil Parkin (4/5/2016)
Gail and I are gamely persevering with this one. I think my pressure limit has been reached now, though.
Oh god...
"The delete works sometimes"
... Surely, please,...
"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 5, 2016 at 11:10 am
Sachin Nandanwar (4/5/2016)
Kishore M. K. (4/5/2016)
Is this Stop-Start of SQL Service is causing IDENTITY value to jump to lower random value ?
This has been a known issue on atleast 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 5, 2016 at 10:19 am
Seems the OP removed the query. Shame. I'd love to see the execution plan. The query, all by itself, didn't seem to have any obvious issues. I'd be curious what...
"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 5, 2016 at 10:17 am
Phil Parkin (4/5/2016)
Gail and I are gamely persevering with this one. I think my pressure limit has been reached now, though.
Oh god...
"The delete works sometimes"
... Surely, please, tell me this...
"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 5, 2016 at 10:13 am
That sounds like an issue with statistics or possibly a bad parameter sniffing issue (or both in combination). Recompiling the procedure causes it to create a new plan based on...
"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 4, 2016 at 5:25 pm
Oh, we're going off memory here. I did run into this issue on 2008r2, but only with a single app. We tracked down which app was having the failure 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
April 4, 2016 at 3:03 pm
I've only seen that error come up in the event of timeouts, or, when we had an app that was using an older version of OLEDB to connect to 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
April 4, 2016 at 1:36 pm
Possibly, but SQL Server isn't going to flush the log in a clockwork, every four minutes, fashion. So I can see how external I/O issues can lead to the log...
"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 4, 2016 at 11:14 am
Viewing 15 posts - 4,876 through 4,890 (of 22,224 total)