February 14, 2011 at 12:27 pm
mw112009 (2/14/2011)
After about 2 hours the result was the same. When I logged in I did not see SSMS running.Why did it shut down on it's own ?
That, I don't know. Have you looked at the error logs?
I didn't see anything in the filelist that seemed wrong.
"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
February 14, 2011 at 3:08 pm
A few things,
Where are you running the management studio from? Is it on your Desktop, or the server where you have the restore running?
Also, what happens if you put this restore into an Agent Job and run it from there?
This way we can try and streamline the issues.
February 14, 2011 at 7:48 pm
Are you logging of an RDP session to the server where the restore is running? If not, why do you have to log back in?
Check your terminal services configuration and see if there is a time out defined for an idle session. If so, this could be logging off your session. If your session is terminated on the server, it will kill the restore process.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
February 15, 2011 at 1:24 pm
Has any thought to look at the Terminal Services Remote Connection Timeout setting? If I am not mistaken it is set by default to 120 minutes.
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
February 16, 2011 at 7:21 am
pankushmehta (2/14/2011)
A few things,Where are you running the management studio from? Is it on your Desktop, or the server where you have the restore running?
Also, what happens if you put this restore into an Agent Job and run it from there?
This way we can try and streamline the issues.
SSMS is installed in the server. I am using a terminal sesion RDP to login to the server.
February 16, 2011 at 7:41 am
Meet George Jetson (2/15/2011)
Has any thought to look at the Terminal Services Remote Connection Timeout setting? If I am not mistaken it is set by default to 120 minutes.
1.) You may be right here.
2.) Yes I was using RDP to login to the server.
3.) The session timeout is set out at 120 minutes. Our restore takes about 70 minutes ( However it can vary but I doubt it it will go above 100 minutes )
Anyhow, we have decided to take the following actions to resolve this issue
1.) Install the OS ( after formatting the hard drive ).
2.) Install SQL-sever
3.) Do the restore. Lets see what happens ??
More later tomorrow.
Viewing 6 posts - 31 through 35 (of 35 total)
You must be logged in to reply to this topic. Login to reply