bsarahim
asked on
Rebuild the whole SQL Server from scratch
Just wanted to understand the process of rebuild the SQL Server in the below situation
windows server 2008 r2 was crashed and rebuilt with scratch and the administrator has given access to me windows admin right.
the currently windows administrator does not have any detailed info about SQL server versions, running, objects, database,etc, and this was connected to ERP
so I found out in the D: Drive it has all the SQL Server folder, which has backup (system/user database, log,etc)
so I need to rebuild it
My Questions here
1. Which Version i need to install the SQL
2. After installation of SQL server
shall i restore the system databases (Master, model,msdb) one by one.. after that shall i move to restore the user database?
After restore the above system database, all my user logins, permission, roles,users, server objects, configuration mg, Ram being used, Sql Configuration mgt port used, etc.. will it be back my original state?
Thanks..
windows server 2008 r2 was crashed and rebuilt with scratch and the administrator has given access to me windows admin right.
the currently windows administrator does not have any detailed info about SQL server versions, running, objects, database,etc, and this was connected to ERP
so I found out in the D: Drive it has all the SQL Server folder, which has backup (system/user database, log,etc)
so I need to rebuild it
My Questions here
1. Which Version i need to install the SQL
2. After installation of SQL server
shall i restore the system databases (Master, model,msdb) one by one.. after that shall i move to restore the user database?
After restore the above system database, all my user logins, permission, roles,users, server objects, configuration mg, Ram being used, Sql Configuration mgt port used, etc.. will it be back my original state?
Thanks..
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks definitely will install all missing patches..
but after new install of system databases I will restore the system db wiith replace/overwritte option and after that I will restore user database
with this above approach all will be normal?? right all users login, permissions, objects, index's, backup schedules, connections, port will work right????
but after new install of system databases I will restore the system db wiith replace/overwritte option and after that I will restore user database
with this above approach all will be normal?? right all users login, permissions, objects, index's, backup schedules, connections, port will work right????
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>> with this above approach all will be normal??
The two most important will be MASTER and MSDB, but should be backing up all system DB's after every change. If you have been doing that, and restoring all system DB's, then yes, it should be back to 'normal', with a couple of caveats...
Go through, check linked servers, check connections, make sure you have the right versions of service providers installed (odbc ado native client, office interfaces, mail interfaces, etc - whatever you use). It is those 'add-ons' and front end apps that may require a separate install or setup / configuration that are often overlooked.
Having said that, you will find a few 'gotchas' here and there. and will need to monitor very closely and be in a position to respond quickly to any hiccups. Expect some.
We have all done a few tweaks here and there without necessarily taking the backups or recording them with a view of having to recover from a catastrophic fail. Until of course, you have gone through such an event, and boy, does that sharpen the processes. That's why a lot of the very good DBA's seem so rigid/ inflexible/ a-retentive with their DB environment.
The two most important will be MASTER and MSDB, but should be backing up all system DB's after every change. If you have been doing that, and restoring all system DB's, then yes, it should be back to 'normal', with a couple of caveats...
Go through, check linked servers, check connections, make sure you have the right versions of service providers installed (odbc ado native client, office interfaces, mail interfaces, etc - whatever you use). It is those 'add-ons' and front end apps that may require a separate install or setup / configuration that are often overlooked.
Having said that, you will find a few 'gotchas' here and there. and will need to monitor very closely and be in a position to respond quickly to any hiccups. Expect some.
We have all done a few tweaks here and there without necessarily taking the backups or recording them with a view of having to recover from a catastrophic fail. Until of course, you have gone through such an event, and boy, does that sharpen the processes. That's why a lot of the very good DBA's seem so rigid/ inflexible/ a-retentive with their DB environment.
ASKER
Thanks a lot for guidance..one quick check
after fresh installation, why cant i just attach the both databases (system & users) instead of restore.. Pls suggest
after fresh installation, why cant i just attach the both databases (system & users) instead of restore.. Pls suggest
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER