July 22, 2011 at 2:32 pm
If I understood correctly your question then there question is regarding disaster recovery.
Question:-
The server crashed. You cannot access anything. And you are given a new box, what will you do?
what is the first thing that is to be done?
Ans:-
After you get new box with Windows and SQL Server installed(not then installed it first) then you have to start to look for latest backup(most likely u need tape backup because old box was no longer you can use) of user database and system database and restore them, fix the login if needed.
July 22, 2011 at 2:46 pm
Thank you! Helps a lot.
July 22, 2011 at 3:02 pm
I would examine the Server that crashed and determine what type of problem it was and take corrective action to resolve the problem.
You want to find out the extent of the problem first on the server that crashed.
Consider the circumstances, in most cases using a new box would be the last resort.
If a backup of the database is needed then I would look for a disk backup if one is available to reduce recovery time.
Depending upon how long the Server Crashed and the backup strategy a disk backup may be available.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
July 22, 2011 at 3:04 pm
Thank you!:-)
July 22, 2011 at 3:11 pm
I think that they were throwing you a bone when you were told that they handed you a new box.
That is just a test of judgement.
If they ask you what corrective actions you should take look back at some of the suggestions that were made by other members and add it to your checklist of action items to take to recover.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
July 22, 2011 at 3:13 pm
OK ,I did not realize that!
July 22, 2011 at 3:28 pm
If they told you that you were not able to log on to the crashed box, you could ask them if the system engineer took a look. Usually when the database server is down, both system engineer and DBA should work together and find out why. If system engineer could not figure it out, building the new box is the option.
--------------------------------------------------------------
DBA or SQL Programmer? Who Knows. :unsure:
July 22, 2011 at 3:33 pm
BCC-493036 (7/22/2011)
If they told you that you were not able to log on to the crashed box, you could ask them if the system engineer took a look. Usually when the database server is down, both system engineer and DBA should work together and find out why. If system engineer could not figure it out, building the new box is the option.
You are assuming that the DBA is not capable of performing that task
I would not suggest that I request assistance from a SE until I took the normal diagnostic steps.
What if you are a DBA and a MCSE and MCITP do you ask for someone to hold you hand?
That would be a rare exception not the norm and if you had to beg for help that would not be a good thing.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
July 22, 2011 at 3:44 pm
Since SVR said "The server crashed. You cannot access anything". it means you could not log on to the server. That is possible. I agree to use disaster recovery first, but you need to be able to log on to the server and then you are able to do troubleshooting.
A good company has alerts system. When the DB server is down both SE and DBA will be notified. They need to work together and figure out the problems. Otherwise, why does the company hire SEs.
--------------------------------------------------------------
DBA or SQL Programmer? Who Knows. :unsure:
July 22, 2011 at 3:53 pm
BCC-493036 (7/22/2011)
Since SVR said "The server crashed. You cannot access anything". it means you could not log on to the server. That is possible. I agree to use disaster recovery first, but you need to be able to log on to the server and then you are able to do troubleshooting.A good company has alerts system. When the DB server is down both SE and DBA will be notified. They need to work together and figure out the problems. Otherwise, why does the company hire System Engineers.
What information do you have?
What if the DBA is a SE?
Even if they are nt they are expected to troubleshoot before crying for help.
Oh please.:w00t:
Call the fire department and ask for help. 😀
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
July 22, 2011 at 3:58 pm
BCC-493036 (7/22/2011)
I do not know if the Windows can be restored to the new server since I'm not a system engineer. But if I get a new server, I will ask if the Windows is installed. If not, the company system engineer should be involved to install it since this is not DBA's responsibilities. After Windows is installed. I'll install SQL server with the same version as the one on the previous server. I'm assuming that the company does not use clustering for SQL server, otherwise, the other node should be up after one node fails. And then I'll restore all databases using full DB backup files plus their transaction log files.
If a Server crashed how could Windows not be installed. :w00t: You are joking, right?
You can't say that this is not at least part of the DBA's responsibilities.
Ask those questions and you get passed over for the job.
This thread is getting very infantile.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
July 22, 2011 at 4:15 pm
SVR (7/22/2011)
Hi,I am new to sql server administration. And I was asked this question in one of my interview.
You are unable to connect to sql server. Where do you look to find out the reason?
After I answered , I will look in the windows logs and try to trouleshoot,
they asked,
The server crashed. You cannot access anything. And you are given a new box, what will you do?
what is the first thing that is to be done?Can anyone give the big picture?
Thanks
SVR
This is a common logic question to understand how you would react under pressure and in the event of a disaster. If you are at the point of bringing up a new box, the crash is significant and you need to get back to "production" ready. Thus think through the steps necessary to get things running again in order to be in production.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 22, 2011 at 4:21 pm
SQLRNNR (7/22/2011)
SVR (7/22/2011)
This is a common logic question to understand how you would react under pressure and in the event of a disaster. If you are at the point of bringing up a new box, the crash is significant and you need to get back to "production" ready. Thus think through the steps necessary to get things running again in order to be in production.
Well stated.
+1
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
July 22, 2011 at 4:23 pm
BCC-493036 (7/22/2011)
Since SVR said "The server crashed. You cannot access anything". it means you could not log on to the server. That is possible. I agree to use disaster recovery first, but you need to be able to log on to the server and then you are able to do troubleshooting.A good company has alerts system. When the DB server is down both SE and DBA will be notified. They need to work together and figure out the problems. Otherwise, why does the company hire SEs.
If you can't log onto a Server you can't troubleshoot? Really? Thanks for sharing that with me.
If a Server Blue Screen or "Crashed" you are not going to get an Alert.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
July 22, 2011 at 4:28 pm
Welsh Corgi (7/22/2011)
If a Server Blue Screen or "Crashed" you are not going to get an Alert.
You are wrong. The alerts will be sent out from monitoring system.
--------------------------------------------------------------
DBA or SQL Programmer? Who Knows. :unsure:
Viewing 15 posts - 16 through 30 (of 40 total)
You must be logged in to reply to this topic. Login to reply