guruesq
asked on
Losing MS SQL DB startup parameters when server is rebooted
We have installed our first clustered SQL server and have noticed that whenever the server is rebooted or loses power, all startup parameters for the master and tempdb are lost and are reset back to some old parameters that we are no longer using. Our only workaround is to reapply the correct startup parameters in Configuration Manager's Advanced Tab and then bring the database online.
Once the database starts, the configured values visible in configuration manager revert back to the incorrect values.
Any help is appreciated.
Once the database starts, the configured values visible in configuration manager revert back to the incorrect values.
Any help is appreciated.
Last Comment
Apparently those settings are are saved in the registry. Have you checked there?
What parameters are you using currently? I am wondring if one of them is over-riding the default options.
What parameters are you using currently? I am wondring if one of them is over-riding the default options.
ASKER
Sorry I've been slow responding to those trying to help us, I'm also being pulled into quite a few meetings throughout the day...
The parameters that we are loosing are the locations on disk of the master and tempdb needed to bring the instance of sql server online.
I've attached a file showing our startup parameters from the physical box that houses the active node in the cluster. We have a production and a development virtual instance of each server in the cluster and the disk files are actually connected via fiber channel to our SAN.
Shown in the image are the correct startup parameters and these parameters are what currently shows in the configuration manager and also via sys.master_files in the database. If the box is rebooted these parameters are overwritten with incorrect values that we haven't used since we are initially installing the server.
Hope this helps a bit. I'll be able to respond more with those helping me in about 4 hours from now after I get out of more meetings.
ConfigMgrStartupParameters.jpg
The parameters that we are loosing are the locations on disk of the master and tempdb needed to bring the instance of sql server online.
I've attached a file showing our startup parameters from the physical box that houses the active node in the cluster. We have a production and a development virtual instance of each server in the cluster and the disk files are actually connected via fiber channel to our SAN.
Shown in the image are the correct startup parameters and these parameters are what currently shows in the configuration manager and also via sys.master_files in the database. If the box is rebooted these parameters are overwritten with incorrect values that we haven't used since we are initially installing the server.
Hope this helps a bit. I'll be able to respond more with those helping me in about 4 hours from now after I get out of more meetings.
ConfigMgrStartupParameters.jpg
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Microsoft SQL Server 2005
Microsoft SQL Server 2005 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. It includes support for managing XML data and allows a database server to be exposed over web services using Tabular Data Stream (TDS) packets encapsulated within SOAP (protocol) requests.
72K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
What sort of startup parameters are you trying to set?