June 20, 2017 at 7:11 am
A colleague was restoring a large backup & asked me why there was a large, red X across the top of the restore screen as it was working. I'd never seen anything like this before, so I thought I'd ask here. Anyone know what that means?
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
June 20, 2017 at 9:47 am
It would be more helpful if you could capture a screen shot of it...
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
June 20, 2017 at 1:32 pm
I've actually seen similar things before. For me, the issue was that SSMS had been running for a long time and I ran out of memory to display the graphics properly for that paricular process.
After that happened, doing almost any SQL query on the same SSMS process would often result in system.outofmemoryexception errors.
My solution was a 2 part solution:
1 - get more RAM in my machine
2 - try not to leave SSMS open for weeks at a time
MIGHT be a different issue, but what you describe sounds exactly like what I saw.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
June 20, 2017 at 3:58 pm
bmg002 - Tuesday, June 20, 2017 1:32 PMI've actually seen similar things before. For me, the issue was that SSMS had been running for a long time and I ran out of memory to display the graphics properly for that paricular process.
After that happened, doing almost any SQL query on the same SSMS process would often result in system.outofmemoryexception errors.
My solution was a 2 part solution:
1 - get more RAM in my machine
2 - try not to leave SSMS open for weeks at a timeMIGHT be a different issue, but what you describe sounds exactly like what I saw.
I've seen precisely the same thing. Since I got a 64-bit machine with decent memory, it hasn't been an issue.
And yes, I'm also guilty of leaving SSMS open for a long time..over a month. Wait, you mean it isn't normal to have it open all the time? 😉
June 20, 2017 at 4:18 pm
Since the person in question was transferring a terrabyte database on a laptop, lack of RAM is likely it. Thanks all!
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
June 20, 2017 at 11:32 pm
Ed Wagner - Tuesday, June 20, 2017 3:58 PMAnd yes, I'm also guilty of leaving SSMS open for a long time..over a month. Wait, you mean it isn't normal to have it open all the time? 😉
I only close SSMS when I get a "Exception of type 'System.OutOfMemoryException' was thrown" or need to reboot my PC
June 21, 2017 at 8:23 am
DesNorton - Tuesday, June 20, 2017 11:32 PMEd Wagner - Tuesday, June 20, 2017 3:58 PMAnd yes, I'm also guilty of leaving SSMS open for a long time..over a month. Wait, you mean it isn't normal to have it open all the time? 😉
I only close SSMS when I get a "Exception of type 'System.OutOfMemoryException' was thrown" or need to reboot my PC
heh... that's actually what I do too... but I generally have 2 or 3 (4 right now) different copies of it running. 2x2016 and 2x2012. I need to use 2012 for our 2012 SSIS catalog. Well, I don't NEED to, but the performance is a LOT nicer. TSQL and database configuration changes I do in 2016 without any problems. I had 1 more open but it had crashed on me :(.
I imagine I'll need to close one of them (or all) befure the end of the week to prevent that out of memory exception.
First time I saw that, I thought it meant the server was out of memory and I thought "I'm not pulling back 64GB of data... why am I getting that error...". turns out it was a local machine thing.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply