I use a database product that utilises MSDE 2000. The database creates a
second database called " databasename_data_1.mdf" database when installed.
I noticed after detaching and moving the database that this secondary
database had not attached correctly. However when I tried to reattach it
using the
exec sp_attach_db command it stated that the "databasename_data_1" already
existed. However when I tried to reattach it using the sp_detach_db command
the error message stated it not exist?
If any one has any ideas?
Peter
"Peter M" <PeterM@.discussions.microsoft.com> wrote in message
news:C2B01189-C78A-4738-A932-18837A63EC16@.microsoft.com...
> I use a database product that utilises MSDE 2000. The database creates a
> second database called " databasename_data_1.mdf" database when
installed.
> I noticed after detaching and moving the database that this secondary
> database had not attached correctly. However when I tried to reattach it
> using the
> exec sp_attach_db command it stated that the "databasename_data_1" already
> existed. However when I tried to reattach it using the sp_detach_db
command
> the error message stated it not exist?
> If any one has any ideas?
> Peter
What does SELECT * FROM sysdatabases tell you?
Rick Sawtell
MCT, MCSD, MCDBA
|||Rick, I will check when back onsite. Do you know much about this
*_data_1.mdf structure. I was not sure if it made a difference when
detaching and reattaching whether one had to be done before the other.
regards
Peter
"Rick Sawtell" wrote:
> "Peter M" <PeterM@.discussions.microsoft.com> wrote in message
> news:C2B01189-C78A-4738-A932-18837A63EC16@.microsoft.com...
> installed.
> command
>
> What does SELECT * FROM sysdatabases tell you?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
Showing posts with label product. Show all posts
Showing posts with label product. Show all posts
Friday, March 23, 2012
MSDE query
I use a database product that utilises MSDE 2000. The database creates a
second database called " databasename_data_1.mdf" database when installed.
I noticed after detaching and moving the database that this secondary
database had not attached correctly. However when I tried to reattach it
using the
exec sp_attach_db command it stated that the "databasename_data_1" already
existed. However when I tried to reattach it using the sp_detach_db command
the error message stated it not exist'
If any one has any ideas'
Peter"Peter M" <PeterM@.discussions.microsoft.com> wrote in message
news:C2B01189-C78A-4738-A932-18837A63EC16@.microsoft.com...
> I use a database product that utilises MSDE 2000. The database creates a
> second database called " databasename_data_1.mdf" database when
installed.
> I noticed after detaching and moving the database that this secondary
> database had not attached correctly. However when I tried to reattach it
> using the
> exec sp_attach_db command it stated that the "databasename_data_1" already
> existed. However when I tried to reattach it using the sp_detach_db
command
> the error message stated it not exist'
> If any one has any ideas'
> Peter
What does SELECT * FROM sysdatabases tell you?
Rick Sawtell
MCT, MCSD, MCDBA|||Rick, I will check when back onsite. Do you know much about this
*_data_1.mdf structure. I was not sure if it made a difference when
detaching and reattaching whether one had to be done before the other.
regards
Peter
"Rick Sawtell" wrote:
> "Peter M" <PeterM@.discussions.microsoft.com> wrote in message
> news:C2B01189-C78A-4738-A932-18837A63EC16@.microsoft.com...
> installed.
> command
>
> What does SELECT * FROM sysdatabases tell you?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
second database called " databasename_data_1.mdf" database when installed.
I noticed after detaching and moving the database that this secondary
database had not attached correctly. However when I tried to reattach it
using the
exec sp_attach_db command it stated that the "databasename_data_1" already
existed. However when I tried to reattach it using the sp_detach_db command
the error message stated it not exist'
If any one has any ideas'
Peter"Peter M" <PeterM@.discussions.microsoft.com> wrote in message
news:C2B01189-C78A-4738-A932-18837A63EC16@.microsoft.com...
> I use a database product that utilises MSDE 2000. The database creates a
> second database called " databasename_data_1.mdf" database when
installed.
> I noticed after detaching and moving the database that this secondary
> database had not attached correctly. However when I tried to reattach it
> using the
> exec sp_attach_db command it stated that the "databasename_data_1" already
> existed. However when I tried to reattach it using the sp_detach_db
command
> the error message stated it not exist'
> If any one has any ideas'
> Peter
What does SELECT * FROM sysdatabases tell you?
Rick Sawtell
MCT, MCSD, MCDBA|||Rick, I will check when back onsite. Do you know much about this
*_data_1.mdf structure. I was not sure if it made a difference when
detaching and reattaching whether one had to be done before the other.
regards
Peter
"Rick Sawtell" wrote:
> "Peter M" <PeterM@.discussions.microsoft.com> wrote in message
> news:C2B01189-C78A-4738-A932-18837A63EC16@.microsoft.com...
> installed.
> command
>
> What does SELECT * FROM sysdatabases tell you?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
MSDE query
I use a database product that utilises MSDE 2000. The database creates a
second database called " databasename_data_1.mdf" database when installed.
I noticed after detaching and moving the database that this secondary
database had not attached correctly. However when I tried to reattach it
using the
exec sp_attach_db command it stated that the "databasename_data_1" already
existed. However when I tried to reattach it using the sp_detach_db command
the error message stated it not exist'
If any one has any ideas'
Peter"Peter M" <PeterM@.discussions.microsoft.com> wrote in message
news:C2B01189-C78A-4738-A932-18837A63EC16@.microsoft.com...
> I use a database product that utilises MSDE 2000. The database creates a
> second database called " databasename_data_1.mdf" database when
installed.
> I noticed after detaching and moving the database that this secondary
> database had not attached correctly. However when I tried to reattach it
> using the
> exec sp_attach_db command it stated that the "databasename_data_1" already
> existed. However when I tried to reattach it using the sp_detach_db
command
> the error message stated it not exist'
> If any one has any ideas'
> Peter
What does SELECT * FROM sysdatabases tell you?
Rick Sawtell
MCT, MCSD, MCDBA|||Rick, I will check when back onsite. Do you know much about this
*_data_1.mdf structure. I was not sure if it made a difference when
detaching and reattaching whether one had to be done before the other.
regards
Peter
"Rick Sawtell" wrote:
> "Peter M" <PeterM@.discussions.microsoft.com> wrote in message
> news:C2B01189-C78A-4738-A932-18837A63EC16@.microsoft.com...
> > I use a database product that utilises MSDE 2000. The database creates a
> > second database called " databasename_data_1.mdf" database when
> installed.
> > I noticed after detaching and moving the database that this secondary
> > database had not attached correctly. However when I tried to reattach it
> > using the
> > exec sp_attach_db command it stated that the "databasename_data_1" already
> > existed. However when I tried to reattach it using the sp_detach_db
> command
> > the error message stated it not exist'
> > If any one has any ideas'
> > Peter
>
> What does SELECT * FROM sysdatabases tell you?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
second database called " databasename_data_1.mdf" database when installed.
I noticed after detaching and moving the database that this secondary
database had not attached correctly. However when I tried to reattach it
using the
exec sp_attach_db command it stated that the "databasename_data_1" already
existed. However when I tried to reattach it using the sp_detach_db command
the error message stated it not exist'
If any one has any ideas'
Peter"Peter M" <PeterM@.discussions.microsoft.com> wrote in message
news:C2B01189-C78A-4738-A932-18837A63EC16@.microsoft.com...
> I use a database product that utilises MSDE 2000. The database creates a
> second database called " databasename_data_1.mdf" database when
installed.
> I noticed after detaching and moving the database that this secondary
> database had not attached correctly. However when I tried to reattach it
> using the
> exec sp_attach_db command it stated that the "databasename_data_1" already
> existed. However when I tried to reattach it using the sp_detach_db
command
> the error message stated it not exist'
> If any one has any ideas'
> Peter
What does SELECT * FROM sysdatabases tell you?
Rick Sawtell
MCT, MCSD, MCDBA|||Rick, I will check when back onsite. Do you know much about this
*_data_1.mdf structure. I was not sure if it made a difference when
detaching and reattaching whether one had to be done before the other.
regards
Peter
"Rick Sawtell" wrote:
> "Peter M" <PeterM@.discussions.microsoft.com> wrote in message
> news:C2B01189-C78A-4738-A932-18837A63EC16@.microsoft.com...
> > I use a database product that utilises MSDE 2000. The database creates a
> > second database called " databasename_data_1.mdf" database when
> installed.
> > I noticed after detaching and moving the database that this secondary
> > database had not attached correctly. However when I tried to reattach it
> > using the
> > exec sp_attach_db command it stated that the "databasename_data_1" already
> > existed. However when I tried to reattach it using the sp_detach_db
> command
> > the error message stated it not exist'
> > If any one has any ideas'
> > Peter
>
> What does SELECT * FROM sysdatabases tell you?
>
> Rick Sawtell
> MCT, MCSD, MCDBA
>
>
Saturday, February 25, 2012
MSDE incomplete install
I have SQL 2000 running on a Windows 2000 server.
A third party product attempted to install MSDE onto the same server, but
failed to complete its install.
At random it appears as though the MSDE attempts to run and complete its
install, which increases the processor upto approx 100%.
Since the MSDE is in an incomplete state, what is the best approach at
attempting to remove the failing component and leave SQL intact.
MSDE does not show up in the add/remove programs.
Regardshi,
Ray wrote:
> I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server,
> but failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete
> its install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
>
first identify the named instance name, perhaps looking in the \Program
Files\Microsoft SQL Server\ folder... as you already have a SQL Server 2000
installed (probably as default instance, check it first), you could have
something like MSSQL$InstanceName...
you can then manually clean up the failed install following
http://support.microsoft.com/defaul...b;EN-US;Q290991 ...
this procedure does not clean up Windows Installer MSDE related registry
entries, and you have to use (if you want to) MSIZap.exe, part of the
Windows Installer SDK as exposed in
http://support.microsoft.com/defaul...kb;en-us;320873
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply|||The reason MSDE doesn't appear in add/remove programs is that the third
party product installed it as a merge module which means as far as the
installer is concerned, it is part of the product you're installing. Try
removing the third party product with add/remove programs.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ray" <Ray@.test.com> wrote in message
news:%23g62vrfiGHA.1600@.TK2MSFTNGP04.phx.gbl...
>I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server, but
> failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete its
> install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
> Regards
>
A third party product attempted to install MSDE onto the same server, but
failed to complete its install.
At random it appears as though the MSDE attempts to run and complete its
install, which increases the processor upto approx 100%.
Since the MSDE is in an incomplete state, what is the best approach at
attempting to remove the failing component and leave SQL intact.
MSDE does not show up in the add/remove programs.
Regardshi,
Ray wrote:
> I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server,
> but failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete
> its install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
>
first identify the named instance name, perhaps looking in the \Program
Files\Microsoft SQL Server\ folder... as you already have a SQL Server 2000
installed (probably as default instance, check it first), you could have
something like MSSQL$InstanceName...
you can then manually clean up the failed install following
http://support.microsoft.com/defaul...b;EN-US;Q290991 ...
this procedure does not clean up Windows Installer MSDE related registry
entries, and you have to use (if you want to) MSIZap.exe, part of the
Windows Installer SDK as exposed in
http://support.microsoft.com/defaul...kb;en-us;320873
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply|||The reason MSDE doesn't appear in add/remove programs is that the third
party product installed it as a merge module which means as far as the
installer is concerned, it is part of the product you're installing. Try
removing the third party product with add/remove programs.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ray" <Ray@.test.com> wrote in message
news:%23g62vrfiGHA.1600@.TK2MSFTNGP04.phx.gbl...
>I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server, but
> failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete its
> install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
> Regards
>
MSDE incomplete install
I have SQL 2000 running on a Windows 2000 server.
A third party product attempted to install MSDE onto the same server, but
failed to complete its install.
At random it appears as though the MSDE attempts to run and complete its
install, which increases the processor upto approx 100%.
Since the MSDE is in an incomplete state, what is the best approach at
attempting to remove the failing component and leave SQL intact.
MSDE does not show up in the add/remove programs.
Regardshi,
Ray wrote:
> I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server,
> but failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete
> its install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
>
first identify the named instance name, perhaps looking in the \Program
Files\Microsoft SQL Server\ folder... as you already have a SQL Server 2000
installed (probably as default instance, check it first), you could have
something like MSSQL$InstanceName...
you can then manually clean up the failed install following
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991 ...
this procedure does not clean up Windows Installer MSDE related registry
entries, and you have to use (if you want to) MSIZap.exe, part of the
Windows Installer SDK as exposed in
http://support.microsoft.com/default.aspx?scid=kb;en-us;320873
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply|||The reason MSDE doesn't appear in add/remove programs is that the third
party product installed it as a merge module which means as far as the
installer is concerned, it is part of the product you're installing. Try
removing the third party product with add/remove programs.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ray" <Ray@.test.com> wrote in message
news:%23g62vrfiGHA.1600@.TK2MSFTNGP04.phx.gbl...
>I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server, but
> failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete its
> install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
> Regards
>
A third party product attempted to install MSDE onto the same server, but
failed to complete its install.
At random it appears as though the MSDE attempts to run and complete its
install, which increases the processor upto approx 100%.
Since the MSDE is in an incomplete state, what is the best approach at
attempting to remove the failing component and leave SQL intact.
MSDE does not show up in the add/remove programs.
Regardshi,
Ray wrote:
> I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server,
> but failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete
> its install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
>
first identify the named instance name, perhaps looking in the \Program
Files\Microsoft SQL Server\ folder... as you already have a SQL Server 2000
installed (probably as default instance, check it first), you could have
something like MSSQL$InstanceName...
you can then manually clean up the failed install following
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q290991 ...
this procedure does not clean up Windows Installer MSDE related registry
entries, and you have to use (if you want to) MSIZap.exe, part of the
Windows Installer SDK as exposed in
http://support.microsoft.com/default.aspx?scid=kb;en-us;320873
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply|||The reason MSDE doesn't appear in add/remove programs is that the third
party product installed it as a merge module which means as far as the
installer is concerned, it is part of the product you're installing. Try
removing the third party product with add/remove programs.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Ray" <Ray@.test.com> wrote in message
news:%23g62vrfiGHA.1600@.TK2MSFTNGP04.phx.gbl...
>I have SQL 2000 running on a Windows 2000 server.
> A third party product attempted to install MSDE onto the same server, but
> failed to complete its install.
> At random it appears as though the MSDE attempts to run and complete its
> install, which increases the processor upto approx 100%.
> Since the MSDE is in an incomplete state, what is the best approach at
> attempting to remove the failing component and leave SQL intact.
> MSDE does not show up in the add/remove programs.
> Regards
>
Subscribe to:
Posts (Atom)