I read earlier posts about restoring the master database.
I am testing for failover, and I found that after I had restored the master
database to the failover server, the SQL Server service stopped immediately
after starting.
The databases on the production server are on a drive which doesn't exist on
the failover server. Is it necessary to configure the servers identically?
I think perhaps SQL Server service can't start because it can't locate the
model database to create the tempdb, or because the path the tempdb doesn't
exist.
I can't get it started even with sqlservr.exe -f, in order to Alter Database
and change the location of the databases.
The Event log had errors (17052, 17204) because the path in sysdatabases
points to a non-existent location.
I am running SQL Server 2000 Standard edition.
Thanks
BillHere is a nice article on moving db locations:
http://support.microsoft.com/defaul...b;en-us;224071.
Check the master db first.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"bill" <belgie@.datamti.com> wrote in message
news:%237QDmlDwEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I read earlier posts about restoring the master database.
> I am testing for failover, and I found that after I had restored the
master
> database to the failover server, the SQL Server service stopped
immediately
> after starting.
> The databases on the production server are on a drive which doesn't exist
on
> the failover server. Is it necessary to configure the servers
identically?
> I think perhaps SQL Server service can't start because it can't locate the
> model database to create the tempdb, or because the path the tempdb
doesn't
> exist.
> I can't get it started even with sqlservr.exe -f, in order to Alter
Database
> and change the location of the databases.
> The Event log had errors (17052, 17204) because the path in sysdatabases
> points to a non-existent location.
> I am running SQL Server 2000 Standard edition.
> Thanks
> Bill
>
>|||Master, Model, and MSDB must be in the same path they originally came from.
Keep in mind though that for reasons unknown to me SQL will shut down after
restoring even to the correct path.
"bill" <belgie@.datamti.com> wrote in message
news:#7QDmlDwEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I read earlier posts about restoring the master database.
> I am testing for failover, and I found that after I had restored the
master
> database to the failover server, the SQL Server service stopped
immediately
> after starting.
> The databases on the production server are on a drive which doesn't exist
on
> the failover server. Is it necessary to configure the servers
identically?
> I think perhaps SQL Server service can't start because it can't locate the
> model database to create the tempdb, or because the path the tempdb
doesn't
> exist.
> I can't get it started even with sqlservr.exe -f, in order to Alter
Database
> and change the location of the databases.
> The Event log had errors (17052, 17204) because the path in sysdatabases
> points to a non-existent location.
> I am running SQL Server 2000 Standard edition.
> Thanks
> Bill
>
>|||Hi
The SQL server log will tell you why it fails to start, but if you are
restoring a master database from a different configuration one of the
problems will be that it can not find the databases.
You hardware should be the same configuration, see "single node failover"
section of
[url]http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx#EJAA[
/url]
John
"bill" wrote:
> I read earlier posts about restoring the master database.
> I am testing for failover, and I found that after I had restored the maste
r
> database to the failover server, the SQL Server service stopped immediatel
y
> after starting.
> The databases on the production server are on a drive which doesn't exist
on
> the failover server. Is it necessary to configure the servers identically
?
> I think perhaps SQL Server service can't start because it can't locate the
> model database to create the tempdb, or because the path the tempdb doesn'
t
> exist.
> I can't get it started even with sqlservr.exe -f, in order to Alter Databa
se
> and change the location of the databases.
> The Event log had errors (17052, 17204) because the path in sysdatabases
> points to a non-existent location.
> I am running SQL Server 2000 Standard edition.
> Thanks
> Bill
>
>sql
Showing posts with label masterdatabase. Show all posts
Showing posts with label masterdatabase. Show all posts
Monday, March 26, 2012
restoring the master database
I read earlier posts about restoring the master database.
I am testing for failover, and I found that after I had restored the master
database to the failover server, the SQL Server service stopped immediately
after starting.
The databases on the production server are on a drive which doesn't exist on
the failover server. Is it necessary to configure the servers identically?
I think perhaps SQL Server service can't start because it can't locate the
model database to create the tempdb, or because the path the tempdb doesn't
exist.
I can't get it started even with sqlservr.exe -f, in order to Alter Database
and change the location of the databases.
The Event log had errors (17052, 17204) because the path in sysdatabases
points to a non-existent location.
I am running SQL Server 2000 Standard edition.
Thanks
Bill
Here is a nice article on moving db locations:
http://support.microsoft.com/default...;en-us;224071.
Check the master db first.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"bill" <belgie@.datamti.com> wrote in message
news:%237QDmlDwEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I read earlier posts about restoring the master database.
> I am testing for failover, and I found that after I had restored the
master
> database to the failover server, the SQL Server service stopped
immediately
> after starting.
> The databases on the production server are on a drive which doesn't exist
on
> the failover server. Is it necessary to configure the servers
identically?
> I think perhaps SQL Server service can't start because it can't locate the
> model database to create the tempdb, or because the path the tempdb
doesn't
> exist.
> I can't get it started even with sqlservr.exe -f, in order to Alter
Database
> and change the location of the databases.
> The Event log had errors (17052, 17204) because the path in sysdatabases
> points to a non-existent location.
> I am running SQL Server 2000 Standard edition.
> Thanks
> Bill
>
>
|||Master, Model, and MSDB must be in the same path they originally came from.
Keep in mind though that for reasons unknown to me SQL will shut down after
restoring even to the correct path.
"bill" <belgie@.datamti.com> wrote in message
news:#7QDmlDwEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I read earlier posts about restoring the master database.
> I am testing for failover, and I found that after I had restored the
master
> database to the failover server, the SQL Server service stopped
immediately
> after starting.
> The databases on the production server are on a drive which doesn't exist
on
> the failover server. Is it necessary to configure the servers
identically?
> I think perhaps SQL Server service can't start because it can't locate the
> model database to create the tempdb, or because the path the tempdb
doesn't
> exist.
> I can't get it started even with sqlservr.exe -f, in order to Alter
Database
> and change the location of the databases.
> The Event log had errors (17052, 17204) because the path in sysdatabases
> points to a non-existent location.
> I am running SQL Server 2000 Standard edition.
> Thanks
> Bill
>
>
|||Hi
The SQL server log will tell you why it fails to start, but if you are
restoring a master database from a different configuration one of the
problems will be that it can not find the databases.
You hardware should be the same configuration, see "single node failover"
section of
http://www.microsoft.com/technet/pro...clus.mspx#EJAA
John
"bill" wrote:
> I read earlier posts about restoring the master database.
> I am testing for failover, and I found that after I had restored the master
> database to the failover server, the SQL Server service stopped immediately
> after starting.
> The databases on the production server are on a drive which doesn't exist on
> the failover server. Is it necessary to configure the servers identically?
> I think perhaps SQL Server service can't start because it can't locate the
> model database to create the tempdb, or because the path the tempdb doesn't
> exist.
> I can't get it started even with sqlservr.exe -f, in order to Alter Database
> and change the location of the databases.
> The Event log had errors (17052, 17204) because the path in sysdatabases
> points to a non-existent location.
> I am running SQL Server 2000 Standard edition.
> Thanks
> Bill
>
>
sql
I am testing for failover, and I found that after I had restored the master
database to the failover server, the SQL Server service stopped immediately
after starting.
The databases on the production server are on a drive which doesn't exist on
the failover server. Is it necessary to configure the servers identically?
I think perhaps SQL Server service can't start because it can't locate the
model database to create the tempdb, or because the path the tempdb doesn't
exist.
I can't get it started even with sqlservr.exe -f, in order to Alter Database
and change the location of the databases.
The Event log had errors (17052, 17204) because the path in sysdatabases
points to a non-existent location.
I am running SQL Server 2000 Standard edition.
Thanks
Bill
Here is a nice article on moving db locations:
http://support.microsoft.com/default...;en-us;224071.
Check the master db first.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"bill" <belgie@.datamti.com> wrote in message
news:%237QDmlDwEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I read earlier posts about restoring the master database.
> I am testing for failover, and I found that after I had restored the
master
> database to the failover server, the SQL Server service stopped
immediately
> after starting.
> The databases on the production server are on a drive which doesn't exist
on
> the failover server. Is it necessary to configure the servers
identically?
> I think perhaps SQL Server service can't start because it can't locate the
> model database to create the tempdb, or because the path the tempdb
doesn't
> exist.
> I can't get it started even with sqlservr.exe -f, in order to Alter
Database
> and change the location of the databases.
> The Event log had errors (17052, 17204) because the path in sysdatabases
> points to a non-existent location.
> I am running SQL Server 2000 Standard edition.
> Thanks
> Bill
>
>
|||Master, Model, and MSDB must be in the same path they originally came from.
Keep in mind though that for reasons unknown to me SQL will shut down after
restoring even to the correct path.
"bill" <belgie@.datamti.com> wrote in message
news:#7QDmlDwEHA.1292@.TK2MSFTNGP10.phx.gbl...
> I read earlier posts about restoring the master database.
> I am testing for failover, and I found that after I had restored the
master
> database to the failover server, the SQL Server service stopped
immediately
> after starting.
> The databases on the production server are on a drive which doesn't exist
on
> the failover server. Is it necessary to configure the servers
identically?
> I think perhaps SQL Server service can't start because it can't locate the
> model database to create the tempdb, or because the path the tempdb
doesn't
> exist.
> I can't get it started even with sqlservr.exe -f, in order to Alter
Database
> and change the location of the databases.
> The Event log had errors (17052, 17204) because the path in sysdatabases
> points to a non-existent location.
> I am running SQL Server 2000 Standard edition.
> Thanks
> Bill
>
>
|||Hi
The SQL server log will tell you why it fails to start, but if you are
restoring a master database from a different configuration one of the
problems will be that it can not find the databases.
You hardware should be the same configuration, see "single node failover"
section of
http://www.microsoft.com/technet/pro...clus.mspx#EJAA
John
"bill" wrote:
> I read earlier posts about restoring the master database.
> I am testing for failover, and I found that after I had restored the master
> database to the failover server, the SQL Server service stopped immediately
> after starting.
> The databases on the production server are on a drive which doesn't exist on
> the failover server. Is it necessary to configure the servers identically?
> I think perhaps SQL Server service can't start because it can't locate the
> model database to create the tempdb, or because the path the tempdb doesn't
> exist.
> I can't get it started even with sqlservr.exe -f, in order to Alter Database
> and change the location of the databases.
> The Event log had errors (17052, 17204) because the path in sysdatabases
> points to a non-existent location.
> I am running SQL Server 2000 Standard edition.
> Thanks
> Bill
>
>
sql
Tuesday, March 20, 2012
Restoring Masterdatabase
I have a problem restoring a masterdatabase (backup) to another server. As i
t
has to be the same build the former server had 8.00.837 which is with
KB810185 installed. The new one has 8.00.760 and need to install KB810185
and the patch is now with build 8.00.859. Can anyone tell me where I can fin
d
KB810185 build 8.00.837 or does it work with the current KB810185?
Best wishesKB810185 is a hot fix post SQL 2K SP3. See:
http://support.microsoft.com/defaul...kb;en-us;821334
8.00.0837 is another hotfix. See:
http://support.microsoft.com/defaul...kb;en-us;823514
Please note that:
A supported hotfix is now available from Microsoft, but it is only intended
to correct the problem that is described in this article. Only apply it to
systems that are experiencing this specific problem. This hotfix may receive
additional testing. Therefore, if you are not severely affected by this
problem, Microsoft recommends that you wait for the next SQL Server 2000
service pack that contains this hotfix.
You did not mention why you need to restore master. If the backup your
master database was created using a 8.00.0837, then you should be able to
restore it using build 8.00.0837. After the restore you can upgrade the
server to a later hotfix.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:77A94361-A1FB-420E-8592-6675826364B2@.microsoft.com...
>I have a problem restoring a masterdatabase (backup) to another server. As
>it
> has to be the same build the former server had 8.00.837 which is with
> KB810185 installed. The new one has 8.00.760 and need to install KB810185
> and the patch is now with build 8.00.859. Can anyone tell me where I can
> find
> KB810185 build 8.00.837 or does it work with the current KB810185?
>
>
> --
> Best wishes
t
has to be the same build the former server had 8.00.837 which is with
KB810185 installed. The new one has 8.00.760 and need to install KB810185
and the patch is now with build 8.00.859. Can anyone tell me where I can fin
d
KB810185 build 8.00.837 or does it work with the current KB810185?
Best wishesKB810185 is a hot fix post SQL 2K SP3. See:
http://support.microsoft.com/defaul...kb;en-us;821334
8.00.0837 is another hotfix. See:
http://support.microsoft.com/defaul...kb;en-us;823514
Please note that:
A supported hotfix is now available from Microsoft, but it is only intended
to correct the problem that is described in this article. Only apply it to
systems that are experiencing this specific problem. This hotfix may receive
additional testing. Therefore, if you are not severely affected by this
problem, Microsoft recommends that you wait for the next SQL Server 2000
service pack that contains this hotfix.
You did not mention why you need to restore master. If the backup your
master database was created using a 8.00.0837, then you should be able to
restore it using build 8.00.0837. After the restore you can upgrade the
server to a later hotfix.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:77A94361-A1FB-420E-8592-6675826364B2@.microsoft.com...
>I have a problem restoring a masterdatabase (backup) to another server. As
>it
> has to be the same build the former server had 8.00.837 which is with
> KB810185 installed. The new one has 8.00.760 and need to install KB810185
> and the patch is now with build 8.00.859. Can anyone tell me where I can
> find
> KB810185 build 8.00.837 or does it work with the current KB810185?
>
>
> --
> Best wishes
Restoring Masterdatabase
I have a problem restoring a masterdatabase (backup) to another server. As it
has to be the same build the former server had 8.00.837 which is with
KB810185 installed. The new one has 8.00.760 and need to install KB810185
and the patch is now with build 8.00.859. Can anyone tell me where I can find
KB810185 build 8.00.837 or does it work with the current KB810185?
Best wishes
KB810185 is a hot fix post SQL 2K SP3. See:
http://support.microsoft.com/default...b;en-us;821334
8.00.0837 is another hotfix. See:
http://support.microsoft.com/default...b;en-us;823514
Please note that:
A supported hotfix is now available from Microsoft, but it is only intended
to correct the problem that is described in this article. Only apply it to
systems that are experiencing this specific problem. This hotfix may receive
additional testing. Therefore, if you are not severely affected by this
problem, Microsoft recommends that you wait for the next SQL Server 2000
service pack that contains this hotfix.
You did not mention why you need to restore master. If the backup your
master database was created using a 8.00.0837, then you should be able to
restore it using build 8.00.0837. After the restore you can upgrade the
server to a later hotfix.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:77A94361-A1FB-420E-8592-6675826364B2@.microsoft.com...
>I have a problem restoring a masterdatabase (backup) to another server. As
>it
> has to be the same build the former server had 8.00.837 which is with
> KB810185 installed. The new one has 8.00.760 and need to install KB810185
> and the patch is now with build 8.00.859. Can anyone tell me where I can
> find
> KB810185 build 8.00.837 or does it work with the current KB810185?
>
>
> --
> Best wishes
has to be the same build the former server had 8.00.837 which is with
KB810185 installed. The new one has 8.00.760 and need to install KB810185
and the patch is now with build 8.00.859. Can anyone tell me where I can find
KB810185 build 8.00.837 or does it work with the current KB810185?
Best wishes
KB810185 is a hot fix post SQL 2K SP3. See:
http://support.microsoft.com/default...b;en-us;821334
8.00.0837 is another hotfix. See:
http://support.microsoft.com/default...b;en-us;823514
Please note that:
A supported hotfix is now available from Microsoft, but it is only intended
to correct the problem that is described in this article. Only apply it to
systems that are experiencing this specific problem. This hotfix may receive
additional testing. Therefore, if you are not severely affected by this
problem, Microsoft recommends that you wait for the next SQL Server 2000
service pack that contains this hotfix.
You did not mention why you need to restore master. If the backup your
master database was created using a 8.00.0837, then you should be able to
restore it using build 8.00.0837. After the restore you can upgrade the
server to a later hotfix.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:77A94361-A1FB-420E-8592-6675826364B2@.microsoft.com...
>I have a problem restoring a masterdatabase (backup) to another server. As
>it
> has to be the same build the former server had 8.00.837 which is with
> KB810185 installed. The new one has 8.00.760 and need to install KB810185
> and the patch is now with build 8.00.859. Can anyone tell me where I can
> find
> KB810185 build 8.00.837 or does it work with the current KB810185?
>
>
> --
> Best wishes
Restoring Masterdatabase
I have a problem restoring a masterdatabase (backup) to another server. As it
has to be the same build the former server had 8.00.837 which is with
KB810185 installed. The new one has 8.00.760 and need to install KB810185
and the patch is now with build 8.00.859. Can anyone tell me where I can find
KB810185 build 8.00.837 or does it work with the current KB810185?
--
Best wishesKB810185 is a hot fix post SQL 2K SP3. See:
http://support.microsoft.com/default.aspx?scid=kb;en-us;821334
8.00.0837 is another hotfix. See:
http://support.microsoft.com/default.aspx?scid=kb;en-us;823514
Please note that:
A supported hotfix is now available from Microsoft, but it is only intended
to correct the problem that is described in this article. Only apply it to
systems that are experiencing this specific problem. This hotfix may receive
additional testing. Therefore, if you are not severely affected by this
problem, Microsoft recommends that you wait for the next SQL Server 2000
service pack that contains this hotfix.
You did not mention why you need to restore master. If the backup your
master database was created using a 8.00.0837, then you should be able to
restore it using build 8.00.0837. After the restore you can upgrade the
server to a later hotfix.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:77A94361-A1FB-420E-8592-6675826364B2@.microsoft.com...
>I have a problem restoring a masterdatabase (backup) to another server. As
>it
> has to be the same build the former server had 8.00.837 which is with
> KB810185 installed. The new one has 8.00.760 and need to install KB810185
> and the patch is now with build 8.00.859. Can anyone tell me where I can
> find
> KB810185 build 8.00.837 or does it work with the current KB810185?
>
>
> --
> Best wishes
has to be the same build the former server had 8.00.837 which is with
KB810185 installed. The new one has 8.00.760 and need to install KB810185
and the patch is now with build 8.00.859. Can anyone tell me where I can find
KB810185 build 8.00.837 or does it work with the current KB810185?
--
Best wishesKB810185 is a hot fix post SQL 2K SP3. See:
http://support.microsoft.com/default.aspx?scid=kb;en-us;821334
8.00.0837 is another hotfix. See:
http://support.microsoft.com/default.aspx?scid=kb;en-us;823514
Please note that:
A supported hotfix is now available from Microsoft, but it is only intended
to correct the problem that is described in this article. Only apply it to
systems that are experiencing this specific problem. This hotfix may receive
additional testing. Therefore, if you are not severely affected by this
problem, Microsoft recommends that you wait for the next SQL Server 2000
service pack that contains this hotfix.
You did not mention why you need to restore master. If the backup your
master database was created using a 8.00.0837, then you should be able to
restore it using build 8.00.0837. After the restore you can upgrade the
server to a later hotfix.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://weblogs.asp.net/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mats" <Mats@.discussions.microsoft.com> wrote in message
news:77A94361-A1FB-420E-8592-6675826364B2@.microsoft.com...
>I have a problem restoring a masterdatabase (backup) to another server. As
>it
> has to be the same build the former server had 8.00.837 which is with
> KB810185 installed. The new one has 8.00.760 and need to install KB810185
> and the patch is now with build 8.00.859. Can anyone tell me where I can
> find
> KB810185 build 8.00.837 or does it work with the current KB810185?
>
>
> --
> Best wishes
Monday, March 12, 2012
Restoring Master Database errors on SQL 2000 SP3a
Hi All
I work in a envoriment where i restore lots of master
database for specfic reason.
The problem i am currently encountering is the following
When i attempt to restore the Master database is SQL
Enterprise Manager (in single user mode) i get a error
box with a title of sql-dmo odbc sqlstate: HY000 and
nothing else.
It then kills the SQL service which i can then restart as
normal but the master database is not restored.
If i attempt to restore via SQL Query Anylzer i just get
connect broken and the SQL service is stopped.
The only way i have found to restore my master database is
to reinstall SQL from scratch which is very time consuming.
Has anyone else seen this and now how to workaround this
issue with out reinstalling SQL
Many Thanks
Martin Cheetham
Hi,
I have never ended up in this situation. I recommend you to try rebuilding
the MASTER database using REBUILDM.EXE rather than reinstalling SQL Server.
After rebulding the master you can restore the database
using the normal procedure
Thanks
Hari
MCDBA
"Martin Cheetham" <martin_cheetham@.yahoo.co.uk> wrote in message
news:237a101c45e86$4c7f5b60$a401280a@.phx.gbl...
> Hi All
> I work in a envoriment where i restore lots of master
> database for specfic reason.
> The problem i am currently encountering is the following
> When i attempt to restore the Master database is SQL
> Enterprise Manager (in single user mode) i get a error
> box with a title of sql-dmo odbc sqlstate: HY000 and
> nothing else.
> It then kills the SQL service which i can then restart as
> normal but the master database is not restored.
> If i attempt to restore via SQL Query Anylzer i just get
> connect broken and the SQL service is stopped.
> The only way i have found to restore my master database is
> to reinstall SQL from scratch which is very time consuming.
> Has anyone else seen this and now how to workaround this
> issue with out reinstalling SQL
> Many Thanks
> Martin Cheetham
I work in a envoriment where i restore lots of master
database for specfic reason.
The problem i am currently encountering is the following
When i attempt to restore the Master database is SQL
Enterprise Manager (in single user mode) i get a error
box with a title of sql-dmo odbc sqlstate: HY000 and
nothing else.
It then kills the SQL service which i can then restart as
normal but the master database is not restored.
If i attempt to restore via SQL Query Anylzer i just get
connect broken and the SQL service is stopped.
The only way i have found to restore my master database is
to reinstall SQL from scratch which is very time consuming.
Has anyone else seen this and now how to workaround this
issue with out reinstalling SQL
Many Thanks
Martin Cheetham
Hi,
I have never ended up in this situation. I recommend you to try rebuilding
the MASTER database using REBUILDM.EXE rather than reinstalling SQL Server.
After rebulding the master you can restore the database
using the normal procedure
Thanks
Hari
MCDBA
"Martin Cheetham" <martin_cheetham@.yahoo.co.uk> wrote in message
news:237a101c45e86$4c7f5b60$a401280a@.phx.gbl...
> Hi All
> I work in a envoriment where i restore lots of master
> database for specfic reason.
> The problem i am currently encountering is the following
> When i attempt to restore the Master database is SQL
> Enterprise Manager (in single user mode) i get a error
> box with a title of sql-dmo odbc sqlstate: HY000 and
> nothing else.
> It then kills the SQL service which i can then restart as
> normal but the master database is not restored.
> If i attempt to restore via SQL Query Anylzer i just get
> connect broken and the SQL service is stopped.
> The only way i have found to restore my master database is
> to reinstall SQL from scratch which is very time consuming.
> Has anyone else seen this and now how to workaround this
> issue with out reinstalling SQL
> Many Thanks
> Martin Cheetham
Restoring Master Database errors on SQL 2000 SP3a
Hi All
I work in a envoriment where i restore lots of master
database for specfic reason.
The problem i am currently encountering is the following
When i attempt to restore the Master database is SQL
Enterprise Manager (in single user mode) i get a error
box with a title of sql-dmo odbc sqlstate: HY000 and
nothing else.
It then kills the SQL service which i can then restart as
normal but the master database is not restored.
If i attempt to restore via SQL Query Anylzer i just get
connect broken and the SQL service is stopped.
The only way i have found to restore my master database is
to reinstall SQL from scratch which is very time consuming.
Has anyone else seen this and now how to workaround this
issue with out reinstalling SQL
Many Thanks
Martin CheethamHi,
I have never ended up in this situation. I recommend you to try rebuilding
the MASTER database using REBUILDM.EXE rather than reinstalling SQL Server.
After rebulding the master you can restore the database
using the normal procedure
Thanks
Hari
MCDBA
"Martin Cheetham" <martin_cheetham@.yahoo.co.uk> wrote in message
news:237a101c45e86$4c7f5b60$a401280a@.phx
.gbl...
> Hi All
> I work in a envoriment where i restore lots of master
> database for specfic reason.
> The problem i am currently encountering is the following
> When i attempt to restore the Master database is SQL
> Enterprise Manager (in single user mode) i get a error
> box with a title of sql-dmo odbc sqlstate: HY000 and
> nothing else.
> It then kills the SQL service which i can then restart as
> normal but the master database is not restored.
> If i attempt to restore via SQL Query Anylzer i just get
> connect broken and the SQL service is stopped.
> The only way i have found to restore my master database is
> to reinstall SQL from scratch which is very time consuming.
> Has anyone else seen this and now how to workaround this
> issue with out reinstalling SQL
> Many Thanks
> Martin Cheetham
I work in a envoriment where i restore lots of master
database for specfic reason.
The problem i am currently encountering is the following
When i attempt to restore the Master database is SQL
Enterprise Manager (in single user mode) i get a error
box with a title of sql-dmo odbc sqlstate: HY000 and
nothing else.
It then kills the SQL service which i can then restart as
normal but the master database is not restored.
If i attempt to restore via SQL Query Anylzer i just get
connect broken and the SQL service is stopped.
The only way i have found to restore my master database is
to reinstall SQL from scratch which is very time consuming.
Has anyone else seen this and now how to workaround this
issue with out reinstalling SQL
Many Thanks
Martin CheethamHi,
I have never ended up in this situation. I recommend you to try rebuilding
the MASTER database using REBUILDM.EXE rather than reinstalling SQL Server.
After rebulding the master you can restore the database
using the normal procedure
Thanks
Hari
MCDBA
"Martin Cheetham" <martin_cheetham@.yahoo.co.uk> wrote in message
news:237a101c45e86$4c7f5b60$a401280a@.phx
.gbl...
> Hi All
> I work in a envoriment where i restore lots of master
> database for specfic reason.
> The problem i am currently encountering is the following
> When i attempt to restore the Master database is SQL
> Enterprise Manager (in single user mode) i get a error
> box with a title of sql-dmo odbc sqlstate: HY000 and
> nothing else.
> It then kills the SQL service which i can then restart as
> normal but the master database is not restored.
> If i attempt to restore via SQL Query Anylzer i just get
> connect broken and the SQL service is stopped.
> The only way i have found to restore my master database is
> to reinstall SQL from scratch which is very time consuming.
> Has anyone else seen this and now how to workaround this
> issue with out reinstalling SQL
> Many Thanks
> Martin Cheetham
Subscribe to:
Posts (Atom)