Dear Colleagues:
This is such an SQL newbie question its not even funny. To begin with,
please forgive my informality as well as my lack of any specific error
messages, etc.. . I think the questions are academic (the specific error
messages and notes are strewn about my desk at work).
Okay, so here I am, I have a shiny new Windows 2003 Advanced server. So I
want to set up a tiny sharepoint team services site, simple enough. Its the
lightweight version that is
included in the Front Page 2002 CD and pooft, instant sharepoint and badda
bing, you have a small website that small workgroups can use. Please note,
this is not a super confidential eyes only website, so if I had lax MSDE
security, it would not keep me awake at night.
So I download the MSDE from Microsoft and realize that I need to provide a
password for the sa account. A switch after setup.exe.
First, is there a way that I can forego this password, that is to say, that
there is a way for me to install MSDE without a service account password.
I provided the password, the install went great, but now I have issues
associating the sharepoint services site to the MSDE. Obviously, the MSDE
needs to know that sharepoint team services is a good boy.
My problem is that I do not see any configuration options in the small MSDE
engine, so the question here is, other than going to SQL 2000 full blown
where I can tweak things, is how to I tell MSDE that
the team services site, via IIS 6 (running in IIS5 mode) is okay to use it.
Ideally, my goal would be to install MSDE without having to provide a
password, but any advice that could be given would be appreciated.
Thanks,
Roger
If you are trying to "configure" the installation of MSDE you need to get a
copy of the enterprise manager from a SQL 2000 CD or something and you can
then use that to connect to the MSDE database and configure it. MSDE itself
does not come with these tools as it is the "lite" version of SQL, but the
enterprise tools can be used with it to configure it.
Hopefully you have an actual SQL 2000 Server on your network somewhere that
you can use to connect to your MSDE database...
HTH.
"Jolly Student" <jolly@.joy.com> wrote in message
news:ifr1d.8926$G03.2990374@.news4.srv.hcvlny.cv.ne t...
> Dear Colleagues:
> This is such an SQL newbie question its not even funny. To begin with,
> please forgive my informality as well as my lack of any specific error
> messages, etc.. . I think the questions are academic (the specific error
> messages and notes are strewn about my desk at work).
> Okay, so here I am, I have a shiny new Windows 2003 Advanced server. So I
> want to set up a tiny sharepoint team services site, simple enough. Its
the
> lightweight version that is
> included in the Front Page 2002 CD and pooft, instant sharepoint and badda
> bing, you have a small website that small workgroups can use. Please note,
> this is not a super confidential eyes only website, so if I had lax MSDE
> security, it would not keep me awake at night.
> So I download the MSDE from Microsoft and realize that I need to provide a
> password for the sa account. A switch after setup.exe.
> First, is there a way that I can forego this password, that is to say,
that
> there is a way for me to install MSDE without a service account password.
> I provided the password, the install went great, but now I have issues
> associating the sharepoint services site to the MSDE. Obviously, the MSDE
> needs to know that sharepoint team services is a good boy.
> My problem is that I do not see any configuration options in the small
MSDE
> engine, so the question here is, other than going to SQL 2000 full blown
> where I can tweak things, is how to I tell MSDE that
> the team services site, via IIS 6 (running in IIS5 mode) is okay to use
it.
> Ideally, my goal would be to install MSDE without having to provide a
> password, but any advice that could be given would be appreciated.
> Thanks,
> Roger
>
Showing posts with label msde. Show all posts
Showing posts with label msde. Show all posts
Tuesday, March 27, 2012
Basic MSDE Setup Question on Windows Server 2003
Dear Colleagues:
This is such an SQL newbie question its not even funny. To begin with,
please forgive my informality as well as my lack of any specific error
messages, etc.. . I think the questions are academic (the specific error
messages and notes are strewn about my desk at work).
Okay, so here I am, I have a shiny new Windows 2003 Advanced server. So I
want to set up a tiny sharepoint team services site, simple enough. Its the
lightweight version that is
included in the Front Page 2002 CD and pooft, instant sharepoint and badda
bing, you have a small website that small workgroups can use. Please note,
this is not a super confidential eyes only website, so if I had lax MSDE
security, it would not keep me awake at night.
So I download the MSDE from Microsoft and realize that I need to provide a
password for the sa account. A switch after setup.exe.
First, is there a way that I can forego this password, that is to say, that
there is a way for me to install MSDE without a service account password.
I provided the password, the install went great, but now I have issues
associating the sharepoint services site to the MSDE. Obviously, the MSDE
needs to know that sharepoint team services is a good boy.
My problem is that I do not see any configuration options in the small MSDE
engine, so the question here is, other than going to SQL 2000 full blown
where I can tweak things, is how to I tell MSDE that
the team services site, via IIS 6 (running in IIS5 mode) is okay to use it.
Ideally, my goal would be to install MSDE without having to provide a
password, but any advice that could be given would be appreciated.
Thanks,
Roger
To my knowledge, there is no way to install MSDE (or the full blown SQL Server, for that matter), without an sa password. It used to be that you could leave it blank, but that is obviously a security risk and that option has been eliminated.
As for your other question, it sounds like what you need to do is grant database access to the system account that your IIS server is running under. To do this, you can use the osql tool.
Go to a command prompt and type:
osql -U sa -S (local)
Note: If you provided an instance name during your installation, you should use (local)\<instance name>
You will be prompted for the password.
Next type the following 2 lines, replacing <account_name> with the name of the windown account that IIS is running under.
sp_grantlogin '<account_name>'
go
At this point, IIS should be able to connect to your MSDE installation. From there, it's hard to say what you might need to do. Presumably you need a database created within the database server. And after that is created you will need to grant database access to the login you created above. You can do that with something like:
sp_grantdbaccess 'Corporate\JeffL', 'Jeff'
GO
sp_addrolemember 'db_owner', 'Jeff'
GO
If you're not familiar with these types of operations, it might be best to install the full-blown SQL Server so that you can use the GUI interface to perform these operations.|||If you are trying to "configure" the installation of MSDE you need to get a
copy of the enterprise manager from a SQL 2000 CD or something and you can
then use that to connect to the MSDE database and configure it. MSDE itself
does not come with these tools as it is the "lite" version of SQL, but the
enterprise tools can be used with it to configure it.
Hopefully you have an actual SQL 2000 Server on your network somewhere that
you can use to connect to your MSDE database...
HTH.
"Jolly Student" <jolly@.joy.com> wrote in message
news:ifr1d.8926$G03.2990374@.news4.srv.hcvlny.cv.ne t...
> Dear Colleagues:
> This is such an SQL newbie question its not even funny. To begin with,
> please forgive my informality as well as my lack of any specific error
> messages, etc.. . I think the questions are academic (the specific error
> messages and notes are strewn about my desk at work).
> Okay, so here I am, I have a shiny new Windows 2003 Advanced server. So I
> want to set up a tiny sharepoint team services site, simple enough. Its
the
> lightweight version that is
> included in the Front Page 2002 CD and pooft, instant sharepoint and badda
> bing, you have a small website that small workgroups can use. Please note,
> this is not a super confidential eyes only website, so if I had lax MSDE
> security, it would not keep me awake at night.
> So I download the MSDE from Microsoft and realize that I need to provide a
> password for the sa account. A switch after setup.exe.
> First, is there a way that I can forego this password, that is to say,
that
> there is a way for me to install MSDE without a service account password.
> I provided the password, the install went great, but now I have issues
> associating the sharepoint services site to the MSDE. Obviously, the MSDE
> needs to know that sharepoint team services is a good boy.
> My problem is that I do not see any configuration options in the small
MSDE
> engine, so the question here is, other than going to SQL 2000 full blown
> where I can tweak things, is how to I tell MSDE that
> the team services site, via IIS 6 (running in IIS5 mode) is okay to use
it.
> Ideally, my goal would be to install MSDE without having to provide a
> password, but any advice that could be given would be appreciated.
> Thanks,
> Roger
>
This is such an SQL newbie question its not even funny. To begin with,
please forgive my informality as well as my lack of any specific error
messages, etc.. . I think the questions are academic (the specific error
messages and notes are strewn about my desk at work).
Okay, so here I am, I have a shiny new Windows 2003 Advanced server. So I
want to set up a tiny sharepoint team services site, simple enough. Its the
lightweight version that is
included in the Front Page 2002 CD and pooft, instant sharepoint and badda
bing, you have a small website that small workgroups can use. Please note,
this is not a super confidential eyes only website, so if I had lax MSDE
security, it would not keep me awake at night.
So I download the MSDE from Microsoft and realize that I need to provide a
password for the sa account. A switch after setup.exe.
First, is there a way that I can forego this password, that is to say, that
there is a way for me to install MSDE without a service account password.
I provided the password, the install went great, but now I have issues
associating the sharepoint services site to the MSDE. Obviously, the MSDE
needs to know that sharepoint team services is a good boy.
My problem is that I do not see any configuration options in the small MSDE
engine, so the question here is, other than going to SQL 2000 full blown
where I can tweak things, is how to I tell MSDE that
the team services site, via IIS 6 (running in IIS5 mode) is okay to use it.
Ideally, my goal would be to install MSDE without having to provide a
password, but any advice that could be given would be appreciated.
Thanks,
Roger
To my knowledge, there is no way to install MSDE (or the full blown SQL Server, for that matter), without an sa password. It used to be that you could leave it blank, but that is obviously a security risk and that option has been eliminated.
As for your other question, it sounds like what you need to do is grant database access to the system account that your IIS server is running under. To do this, you can use the osql tool.
Go to a command prompt and type:
osql -U sa -S (local)
Note: If you provided an instance name during your installation, you should use (local)\<instance name>
You will be prompted for the password.
Next type the following 2 lines, replacing <account_name> with the name of the windown account that IIS is running under.
sp_grantlogin '<account_name>'
go
At this point, IIS should be able to connect to your MSDE installation. From there, it's hard to say what you might need to do. Presumably you need a database created within the database server. And after that is created you will need to grant database access to the login you created above. You can do that with something like:
sp_grantdbaccess 'Corporate\JeffL', 'Jeff'
GO
sp_addrolemember 'db_owner', 'Jeff'
GO
If you're not familiar with these types of operations, it might be best to install the full-blown SQL Server so that you can use the GUI interface to perform these operations.|||If you are trying to "configure" the installation of MSDE you need to get a
copy of the enterprise manager from a SQL 2000 CD or something and you can
then use that to connect to the MSDE database and configure it. MSDE itself
does not come with these tools as it is the "lite" version of SQL, but the
enterprise tools can be used with it to configure it.
Hopefully you have an actual SQL 2000 Server on your network somewhere that
you can use to connect to your MSDE database...
HTH.
"Jolly Student" <jolly@.joy.com> wrote in message
news:ifr1d.8926$G03.2990374@.news4.srv.hcvlny.cv.ne t...
> Dear Colleagues:
> This is such an SQL newbie question its not even funny. To begin with,
> please forgive my informality as well as my lack of any specific error
> messages, etc.. . I think the questions are academic (the specific error
> messages and notes are strewn about my desk at work).
> Okay, so here I am, I have a shiny new Windows 2003 Advanced server. So I
> want to set up a tiny sharepoint team services site, simple enough. Its
the
> lightweight version that is
> included in the Front Page 2002 CD and pooft, instant sharepoint and badda
> bing, you have a small website that small workgroups can use. Please note,
> this is not a super confidential eyes only website, so if I had lax MSDE
> security, it would not keep me awake at night.
> So I download the MSDE from Microsoft and realize that I need to provide a
> password for the sa account. A switch after setup.exe.
> First, is there a way that I can forego this password, that is to say,
that
> there is a way for me to install MSDE without a service account password.
> I provided the password, the install went great, but now I have issues
> associating the sharepoint services site to the MSDE. Obviously, the MSDE
> needs to know that sharepoint team services is a good boy.
> My problem is that I do not see any configuration options in the small
MSDE
> engine, so the question here is, other than going to SQL 2000 full blown
> where I can tweak things, is how to I tell MSDE that
> the team services site, via IIS 6 (running in IIS5 mode) is okay to use
it.
> Ideally, my goal would be to install MSDE without having to provide a
> password, but any advice that could be given would be appreciated.
> Thanks,
> Roger
>
Basic MSDE Setup Question on Windows Server 2003
Dear Colleagues:
This is such an SQL newbie question its not even funny. To begin with,
please forgive my informality as well as my lack of any specific error
messages, etc.. . I think the questions are academic (the specific error
messages and notes are strewn about my desk at work).
Okay, so here I am, I have a shiny new Windows 2003 Advanced server. So I
want to set up a tiny sharepoint team services site, simple enough. Its the
lightweight version that is
included in the Front Page 2002 CD and pooft, instant sharepoint and badda
bing, you have a small website that small workgroups can use. Please note,
this is not a super confidential eyes only website, so if I had lax MSDE
security, it would not keep me awake at night.
So I download the MSDE from Microsoft and realize that I need to provide a
password for the sa account. A switch after setup.exe.
First, is there a way that I can forego this password, that is to say, that
there is a way for me to install MSDE without a service account password.
I provided the password, the install went great, but now I have issues
associating the sharepoint services site to the MSDE. Obviously, the MSDE
needs to know that sharepoint team services is a good boy.
My problem is that I do not see any configuration options in the small MSDE
engine, so the question here is, other than going to SQL 2000 full blown
where I can tweak things, is how to I tell MSDE that
the team services site, via IIS 6 (running in IIS5 mode) is okay to use it.
Ideally, my goal would be to install MSDE without having to provide a
password, but any advice that could be given would be appreciated.
Thanks,
Roger
If you are trying to "configure" the installation of MSDE you need to get a
copy of the enterprise manager from a SQL 2000 CD or something and you can
then use that to connect to the MSDE database and configure it. MSDE itself
does not come with these tools as it is the "lite" version of SQL, but the
enterprise tools can be used with it to configure it.
Hopefully you have an actual SQL 2000 Server on your network somewhere that
you can use to connect to your MSDE database...
HTH.
"Jolly Student" <jolly@.joy.com> wrote in message
news:ifr1d.8926$G03.2990374@.news4.srv.hcvlny.cv.ne t...
> Dear Colleagues:
> This is such an SQL newbie question its not even funny. To begin with,
> please forgive my informality as well as my lack of any specific error
> messages, etc.. . I think the questions are academic (the specific error
> messages and notes are strewn about my desk at work).
> Okay, so here I am, I have a shiny new Windows 2003 Advanced server. So I
> want to set up a tiny sharepoint team services site, simple enough. Its
the
> lightweight version that is
> included in the Front Page 2002 CD and pooft, instant sharepoint and badda
> bing, you have a small website that small workgroups can use. Please note,
> this is not a super confidential eyes only website, so if I had lax MSDE
> security, it would not keep me awake at night.
> So I download the MSDE from Microsoft and realize that I need to provide a
> password for the sa account. A switch after setup.exe.
> First, is there a way that I can forego this password, that is to say,
that
> there is a way for me to install MSDE without a service account password.
> I provided the password, the install went great, but now I have issues
> associating the sharepoint services site to the MSDE. Obviously, the MSDE
> needs to know that sharepoint team services is a good boy.
> My problem is that I do not see any configuration options in the small
MSDE
> engine, so the question here is, other than going to SQL 2000 full blown
> where I can tweak things, is how to I tell MSDE that
> the team services site, via IIS 6 (running in IIS5 mode) is okay to use
it.
> Ideally, my goal would be to install MSDE without having to provide a
> password, but any advice that could be given would be appreciated.
> Thanks,
> Roger
>
sql
This is such an SQL newbie question its not even funny. To begin with,
please forgive my informality as well as my lack of any specific error
messages, etc.. . I think the questions are academic (the specific error
messages and notes are strewn about my desk at work).
Okay, so here I am, I have a shiny new Windows 2003 Advanced server. So I
want to set up a tiny sharepoint team services site, simple enough. Its the
lightweight version that is
included in the Front Page 2002 CD and pooft, instant sharepoint and badda
bing, you have a small website that small workgroups can use. Please note,
this is not a super confidential eyes only website, so if I had lax MSDE
security, it would not keep me awake at night.
So I download the MSDE from Microsoft and realize that I need to provide a
password for the sa account. A switch after setup.exe.
First, is there a way that I can forego this password, that is to say, that
there is a way for me to install MSDE without a service account password.
I provided the password, the install went great, but now I have issues
associating the sharepoint services site to the MSDE. Obviously, the MSDE
needs to know that sharepoint team services is a good boy.
My problem is that I do not see any configuration options in the small MSDE
engine, so the question here is, other than going to SQL 2000 full blown
where I can tweak things, is how to I tell MSDE that
the team services site, via IIS 6 (running in IIS5 mode) is okay to use it.
Ideally, my goal would be to install MSDE without having to provide a
password, but any advice that could be given would be appreciated.
Thanks,
Roger
If you are trying to "configure" the installation of MSDE you need to get a
copy of the enterprise manager from a SQL 2000 CD or something and you can
then use that to connect to the MSDE database and configure it. MSDE itself
does not come with these tools as it is the "lite" version of SQL, but the
enterprise tools can be used with it to configure it.
Hopefully you have an actual SQL 2000 Server on your network somewhere that
you can use to connect to your MSDE database...
HTH.
"Jolly Student" <jolly@.joy.com> wrote in message
news:ifr1d.8926$G03.2990374@.news4.srv.hcvlny.cv.ne t...
> Dear Colleagues:
> This is such an SQL newbie question its not even funny. To begin with,
> please forgive my informality as well as my lack of any specific error
> messages, etc.. . I think the questions are academic (the specific error
> messages and notes are strewn about my desk at work).
> Okay, so here I am, I have a shiny new Windows 2003 Advanced server. So I
> want to set up a tiny sharepoint team services site, simple enough. Its
the
> lightweight version that is
> included in the Front Page 2002 CD and pooft, instant sharepoint and badda
> bing, you have a small website that small workgroups can use. Please note,
> this is not a super confidential eyes only website, so if I had lax MSDE
> security, it would not keep me awake at night.
> So I download the MSDE from Microsoft and realize that I need to provide a
> password for the sa account. A switch after setup.exe.
> First, is there a way that I can forego this password, that is to say,
that
> there is a way for me to install MSDE without a service account password.
> I provided the password, the install went great, but now I have issues
> associating the sharepoint services site to the MSDE. Obviously, the MSDE
> needs to know that sharepoint team services is a good boy.
> My problem is that I do not see any configuration options in the small
MSDE
> engine, so the question here is, other than going to SQL 2000 full blown
> where I can tweak things, is how to I tell MSDE that
> the team services site, via IIS 6 (running in IIS5 mode) is okay to use
it.
> Ideally, my goal would be to install MSDE without having to provide a
> password, but any advice that could be given would be appreciated.
> Thanks,
> Roger
>
sql
Sunday, March 25, 2012
Basic "getting started" Info on MSDE 2000?
Hello,
I am looking for basic info on installing and using MSDE.
I am trying to install and play with MSDE on my PC (Win2000). I
finally managed to work my way through installation, and named
instances but I am finding no information on how to simply START the
database engine and get to a sql prompt! I have manually started the
MSSQL and SQLAGENT services, and tried running sqlservr.exe and
osql.exe (just guessing) without success. Can anyone refer me to a
document that gives this BASIC information!?(bidalah@.yahoo.com) writes:
> I am looking for basic info on installing and using MSDE.
> I am trying to install and play with MSDE on my PC (Win2000). I
> finally managed to work my way through installation, and named
> instances but I am finding no information on how to simply START the
> database engine and get to a sql prompt! I have manually started the
> MSSQL and SQLAGENT services, and tried running sqlservr.exe and
> osql.exe (just guessing) without success. Can anyone refer me to a
> document that gives this BASIC information!?
SQL Server runs as a service, and you should start it from the
Services Applet in the Control Panel (under Administrative tools). I
don't if you get SQL Server Manager with MSDE; if you do, you can use
this tool a well. The same applies to SQL Server Agent.
You can start sqlservr.exe from the command line, but this is advanced
usage.
OSQL is a client, and this you run from the command line. To connect
with integrated security say:
osql -E -S .\INSTANCENAME
replace INSTANCENAME with the actual name of your instance.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
Sunday, March 11, 2012
Bacon in the fire
I have installed MSDE sp3 with the SAPWD and DISABLENETWORKPROTOCOLS=0
switches set. The server works fine on the local machine but attempts to
access it respond with a 'server does not exist or access denied' message.
How do I verify (via osql) that the NetLib is installed correctly for
TCP/IP? If it is not how do I configure it?
Semper Fi,
Red
Please post to newsgroup only
hi Stephen,
"Stephen J Bement" <spam@.null.net> ha scritto nel messaggio
news:%23RtoNK$nEHA.708@.TK2MSFTNGP09.phx.gbl
> I have installed MSDE sp3 with the SAPWD and DISABLENETWORKPROTOCOLS=0
> switches set. The server works fine on the local machine but attempts
> to access it respond with a 'server does not exist or access denied'
> message.
> How do I verify (via osql) that the NetLib is installed correctly for
> TCP/IP? If it is not how do I configure it?
if you are running Windows XP service pack 2, perhaps
http://support.microsoft.com/default.aspx?kbid=841249 is worth reading
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||the system is running XP sp1 not sp2. It does not have any firewall software
running. It can connect to the Server system (i.e. connect drives copy files
and PCAnywhere) but cannot communicate with the SQL Server.
TIA
Semper Fi,
Red
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2rb1i1F17ftttU1@.uni-berlin.de...
> hi Stephen,
> "Stephen J Bement" <spam@.null.net> ha scritto nel messaggio
> news:%23RtoNK$nEHA.708@.TK2MSFTNGP09.phx.gbl
> if you are running Windows XP service pack 2, perhaps
> http://support.microsoft.com/default.aspx?kbid=841249 is worth reading
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||You might want to check out following article.
BUG: You may not be able to connect to an instance of Microsoft SQL Server
2000 Desktop Engine SP3a or to an instance of Microsoft SQL Server 2000
Desktop Engine (Windows) after you enable the server network libraries
http://support.microsoft.com/?id=827204
To checkout if network libraries are enabled, you can just see errorlog and
see if SQL Server is listening on named pipe and tcp/ip libraries.
switches set. The server works fine on the local machine but attempts to
access it respond with a 'server does not exist or access denied' message.
How do I verify (via osql) that the NetLib is installed correctly for
TCP/IP? If it is not how do I configure it?
Semper Fi,
Red
Please post to newsgroup only
hi Stephen,
"Stephen J Bement" <spam@.null.net> ha scritto nel messaggio
news:%23RtoNK$nEHA.708@.TK2MSFTNGP09.phx.gbl
> I have installed MSDE sp3 with the SAPWD and DISABLENETWORKPROTOCOLS=0
> switches set. The server works fine on the local machine but attempts
> to access it respond with a 'server does not exist or access denied'
> message.
> How do I verify (via osql) that the NetLib is installed correctly for
> TCP/IP? If it is not how do I configure it?
if you are running Windows XP service pack 2, perhaps
http://support.microsoft.com/default.aspx?kbid=841249 is worth reading
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||the system is running XP sp1 not sp2. It does not have any firewall software
running. It can connect to the Server system (i.e. connect drives copy files
and PCAnywhere) but cannot communicate with the SQL Server.
TIA
Semper Fi,
Red
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2rb1i1F17ftttU1@.uni-berlin.de...
> hi Stephen,
> "Stephen J Bement" <spam@.null.net> ha scritto nel messaggio
> news:%23RtoNK$nEHA.708@.TK2MSFTNGP09.phx.gbl
> if you are running Windows XP service pack 2, perhaps
> http://support.microsoft.com/default.aspx?kbid=841249 is worth reading
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||You might want to check out following article.
BUG: You may not be able to connect to an instance of Microsoft SQL Server
2000 Desktop Engine SP3a or to an instance of Microsoft SQL Server 2000
Desktop Engine (Windows) after you enable the server network libraries
http://support.microsoft.com/?id=827204
To checkout if network libraries are enabled, you can just see errorlog and
see if SQL Server is listening on named pipe and tcp/ip libraries.
Thursday, March 8, 2012
Backupstrategy for Database with Merge-Push Replication.
I have a database on a MSSQL 2000 Server which is replicated by a merge push
replication to approximately 20 Notebooks running MSDE.
backup on the Server is done once per night.
If I decide to go back one night on the server, changes which have been
replicated on the notebooks since then will be reapllied.
Is there a strategy better then stopping publication to all notebooks ,
restoring the backup on the server and repushing the publication to the
clients afterwards?Norbert,
Your plan sounds good to me, can't think of a better way.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Kraft, Norbert wrote:
> I have a database on a MSSQL 2000 Server which is replicated by a merge pu
sh
> replication to approximately 20 Notebooks running MSDE.
> backup on the Server is done once per night.
> If I decide to go back one night on the server, changes which have been
> replicated on the notebooks since then will be reapllied.
> Is there a strategy better then stopping publication to all notebooks ,
> restoring the backup on the server and repushing the publication to the
> clients afterwards?
>
>|||Sounds to be a very cumbersom procedure if done by hand. Anyone who had
prepared a sql-DMO script for a similar case ?
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:%23wQQT%23T$EHA.3588@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Norbert,
> Your plan sounds good to me, can't think of a better way.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Kraft, Norbert wrote:
push[vbcol=seagreen]
replication to approximately 20 Notebooks running MSDE.
backup on the Server is done once per night.
If I decide to go back one night on the server, changes which have been
replicated on the notebooks since then will be reapllied.
Is there a strategy better then stopping publication to all notebooks ,
restoring the backup on the server and repushing the publication to the
clients afterwards?Norbert,
Your plan sounds good to me, can't think of a better way.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Kraft, Norbert wrote:
> I have a database on a MSSQL 2000 Server which is replicated by a merge pu
sh
> replication to approximately 20 Notebooks running MSDE.
> backup on the Server is done once per night.
> If I decide to go back one night on the server, changes which have been
> replicated on the notebooks since then will be reapllied.
> Is there a strategy better then stopping publication to all notebooks ,
> restoring the backup on the server and repushing the publication to the
> clients afterwards?
>
>|||Sounds to be a very cumbersom procedure if done by hand. Anyone who had
prepared a sql-DMO script for a similar case ?
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:%23wQQT%23T$EHA.3588@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Norbert,
> Your plan sounds good to me, can't think of a better way.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Kraft, Norbert wrote:
push[vbcol=seagreen]
Backupstrategy for Database with Merge-Push Replication.
I have a database on a MSSQL 2000 Server which is replicated by a merge push
replication to approximately 20 Notebooks running MSDE.
backup on the Server is done once per night.
If I decide to go back one night on the server, changes which have been
replicated on the notebooks since then will be reapllied.
Is there a strategy better then stopping publication to all notebooks ,
restoring the backup on the server and repushing the publication to the
clients afterwards?Norbert,
Your plan sounds good to me, can't think of a better way.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Kraft, Norbert wrote:
> I have a database on a MSSQL 2000 Server which is replicated by a merge push
> replication to approximately 20 Notebooks running MSDE.
> backup on the Server is done once per night.
> If I decide to go back one night on the server, changes which have been
> replicated on the notebooks since then will be reapllied.
> Is there a strategy better then stopping publication to all notebooks ,
> restoring the backup on the server and repushing the publication to the
> clients afterwards?
>
>|||Sounds to be a very cumbersom procedure if done by hand. Anyone who had
prepared a sql-DMO script for a similar case ?
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:%23wQQT%23T$EHA.3588@.TK2MSFTNGP10.phx.gbl...
> Norbert,
> Your plan sounds good to me, can't think of a better way.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Kraft, Norbert wrote:
> > I have a database on a MSSQL 2000 Server which is replicated by a merge
push
> > replication to approximately 20 Notebooks running MSDE.
> > backup on the Server is done once per night.
> > If I decide to go back one night on the server, changes which have been
> > replicated on the notebooks since then will be reapllied.
> > Is there a strategy better then stopping publication to all notebooks ,
> > restoring the backup on the server and repushing the publication to the
> > clients afterwards?
> >
> >
> >
replication to approximately 20 Notebooks running MSDE.
backup on the Server is done once per night.
If I decide to go back one night on the server, changes which have been
replicated on the notebooks since then will be reapllied.
Is there a strategy better then stopping publication to all notebooks ,
restoring the backup on the server and repushing the publication to the
clients afterwards?Norbert,
Your plan sounds good to me, can't think of a better way.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Kraft, Norbert wrote:
> I have a database on a MSSQL 2000 Server which is replicated by a merge push
> replication to approximately 20 Notebooks running MSDE.
> backup on the Server is done once per night.
> If I decide to go back one night on the server, changes which have been
> replicated on the notebooks since then will be reapllied.
> Is there a strategy better then stopping publication to all notebooks ,
> restoring the backup on the server and repushing the publication to the
> clients afterwards?
>
>|||Sounds to be a very cumbersom procedure if done by hand. Anyone who had
prepared a sql-DMO script for a similar case ?
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:%23wQQT%23T$EHA.3588@.TK2MSFTNGP10.phx.gbl...
> Norbert,
> Your plan sounds good to me, can't think of a better way.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Kraft, Norbert wrote:
> > I have a database on a MSSQL 2000 Server which is replicated by a merge
push
> > replication to approximately 20 Notebooks running MSDE.
> > backup on the Server is done once per night.
> > If I decide to go back one night on the server, changes which have been
> > replicated on the notebooks since then will be reapllied.
> > Is there a strategy better then stopping publication to all notebooks ,
> > restoring the backup on the server and repushing the publication to the
> > clients afterwards?
> >
> >
> >
Backupstrategy for Database with Merge-Push Replication.
I have a database on a MSSQL 2000 Server which is replicated by a merge push
replication to approximately 20 Notebooks running MSDE.
backup on the Server is done once per night.
If I decide to go back one night on the server, changes which have been
replicated on the notebooks since then will be reapllied.
Is there a strategy better then stopping publication to all notebooks ,
restoring the backup on the server and repushing the publication to the
clients afterwards?
Norbert,
Your plan sounds good to me, can't think of a better way.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Kraft, Norbert wrote:
> I have a database on a MSSQL 2000 Server which is replicated by a merge push
> replication to approximately 20 Notebooks running MSDE.
> backup on the Server is done once per night.
> If I decide to go back one night on the server, changes which have been
> replicated on the notebooks since then will be reapllied.
> Is there a strategy better then stopping publication to all notebooks ,
> restoring the backup on the server and repushing the publication to the
> clients afterwards?
>
>
|||Sounds to be a very cumbersom procedure if done by hand. Anyone who had
prepared a sql-DMO script for a similar case ?
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:%23wQQT%23T$EHA.3588@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Norbert,
> Your plan sounds good to me, can't think of a better way.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Kraft, Norbert wrote:
push[vbcol=seagreen]
replication to approximately 20 Notebooks running MSDE.
backup on the Server is done once per night.
If I decide to go back one night on the server, changes which have been
replicated on the notebooks since then will be reapllied.
Is there a strategy better then stopping publication to all notebooks ,
restoring the backup on the server and repushing the publication to the
clients afterwards?
Norbert,
Your plan sounds good to me, can't think of a better way.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Kraft, Norbert wrote:
> I have a database on a MSSQL 2000 Server which is replicated by a merge push
> replication to approximately 20 Notebooks running MSDE.
> backup on the Server is done once per night.
> If I decide to go back one night on the server, changes which have been
> replicated on the notebooks since then will be reapllied.
> Is there a strategy better then stopping publication to all notebooks ,
> restoring the backup on the server and repushing the publication to the
> clients afterwards?
>
>
|||Sounds to be a very cumbersom procedure if done by hand. Anyone who had
prepared a sql-DMO script for a similar case ?
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:%23wQQT%23T$EHA.3588@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Norbert,
> Your plan sounds good to me, can't think of a better way.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Kraft, Norbert wrote:
push[vbcol=seagreen]
Friday, February 24, 2012
backupRestore progress bar
Hi,
My app uses MSDE and I have created a UI for user which has buttons to backup and restore the database. Everything works fine but I want to give a visual display to user about the progress of the operation. You know like a progress bar indicating how mu
ch work is done.. so the question is:
Is there a way to find out how much time backup/restore will take.. does sql server provide any such event to us telling this information. I just want to trap this event and give the progress indication to my loyal users.
Thanks all.
dev
Thanks Andrea for the reply. I am using T-SQL commands right now to backup and restore database. If I use sql-dmo to trap progress event then would that mean that I will have to change the backup/restore sourcecode also to use sql-dmo. Please confirm.
Thanks
|||hi,
"dev" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:8CD41CBC-6EF7-46F8-BC3C-3415F14A6BD5@.microsoft.com...
> Thanks Andrea for the reply. I am using T-SQL commands right now to
backup
>and restore database. If I use sql-dmo to trap progress event then would
that
>mean that I will have to change the backup/restore sourcecode also to use
>sql-dmo. Please confirm.
yep.. you have to use the SQL-DMO backup object to trap the raised events...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||oh no.. so what is this sql-dmo. What is the purpose of it's existance. Why do we need it (besides for the progress bar). How is it different from programming with T-SQL. How can we choose which way to go, T-SQL or SQL-DMO. What are it's advantages an
d disadvantages.
Thanks
|||Also was it unwise of me to opt for T-SQL for doing everything instead of going for DMO. And is it ok to use DMO for backup/restore and use T-SQL for everything else. What are your recommendations.
We are as before an ISV, app will be deployed using MSDE, will have max a couple of databases. Will provide an interface to the user to backup and restore database. Will creare database from app and do version checks for database.
What should we do... or should we wait for SMO..
Thanks for your valuable time.
|||hi,
"dev" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:07DA4684-529D-48D5-9D6A-56DDFDB077A7@.microsoft.com...
> oh no.. so what is this sql-dmo. What is the purpose of it's existance.
Why do we need it
>(besides for the progress bar). How is it different from programming with
T-SQL. How can
> we choose which way to go, T-SQL or SQL-DMO. What are it's advantages and
disadvantages.
> Thanks
SQL-DMO is an acronym for SQL Distributed Management Object and is a full
object model to manage and administer SQL Server..
it exposes a nice object model you can navigate to perform quiet all
management tasks on SQL Server..
it's not designed for data manipulation even if it provides some features
to.
it comes with MSDE and/or can be installed from the Client Tools
installation package of SQL Server.
it is not provided as a separate download and/or package, so you have to
depoly it yourself in MSDE scenarios (you are legitimate to) ... this can be
count as a disadvantage too :-)
it's a little buggy =;-) and eats a lot of memory, but is very handy for
some admin scenario...
Transact-SQL, on the contrary, is the language SQL Server better understand,
and can perform both data manipulation and administration tasks... it's a
separate language where DMO is just a COM object model you can use in any
COM compliant client, so they can not be compared... you shoul'd stick with
Transact-SQL, and use DMO where and when appropriated...
by the way... there's only 1 book worth reading about SQL-DMO, by SQL Server
MVPs Allan Mitchell and Mark Allison,
http://www.compman.co.uk/cgi-win/browse.exe?ref=552118 , which I personally
recommend reading...
FWIW, you can have a look at a free prj of mine at the link following my
sign to have an idea aboout what you can do with SQL-DMO, a prj that
provides a user interface similar to Enteprise Manager written in VB6
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi,
"dev" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:AF907AC5-9610-41F9-95DD-FC68828844F6@.microsoft.com...
> Also was it unwise of me to opt for T-SQL for doing everything instead of
going for DMO.
>And is it ok to use DMO for backup/restore and use T-SQL for everything
else. What are your
>recommendations.
> We are as before an ISV, app will be deployed using MSDE, will have max a
couple of
>databases. Will provide an interface to the user to backup and restore
database.
>Will creare database from app and do version checks for database.
> What should we do... or should we wait for SMO..
if you only need DMO for presenting a progress bar indicating backup
progress, let it be...
you have to talk to SQL Server via Transact-SQL...
perform backup via ADO.Net commands...
SMO will be only available wit SQL Server 2005, and anyway I don't think it
shoul'd be used for traditional programming, but for the same things now
covered by DMO...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea for the insight. I already use your tool since quiet some time and appreciate it. So do you recommend I use T-SQL for everything as now, you know db creation, data manipulation and use dmo for backup/restore which I can later port to use s
mo when yukon arrives..
dev
|||I am sorry Andrea but I didn't understand what you said here:
"if you only need DMO for presenting a progress bar indicating backup
progress, let it be...
you have to talk to SQL Server via Transact-SQL...
perform backup via ADO.Net commands..."
Do you mean that I use T-SQL for everything else and just use DMO for the backup/restore.
Sorry to bother you like this but Thanks
|||hi,
"dev" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:778938C6-1142-4954-B633-BBF0669342D3@.microsoft.com...
> I am sorry Andrea but I didn't understand what you said here:
> "if you only need DMO for presenting a progress bar indicating backup
> progress, let it be...
> you have to talk to SQL Server via Transact-SQL...
> perform backup via ADO.Net commands..."
> Do you mean that I use T-SQL for everything else and just use DMO for the
backup/restore.
> Sorry to bother you like this but Thanks
please excuse my poor english...
what I mean is go with Transact-SQL for all you stuffs, including
Backup/Restore, if you only need SQL-DMO for providing a progress
indicator...
if you need SQL-DMO for other things, then you can consider adding it to
your project references [and setup package :-( ]
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
My app uses MSDE and I have created a UI for user which has buttons to backup and restore the database. Everything works fine but I want to give a visual display to user about the progress of the operation. You know like a progress bar indicating how mu
ch work is done.. so the question is:
Is there a way to find out how much time backup/restore will take.. does sql server provide any such event to us telling this information. I just want to trap this event and give the progress indication to my loyal users.
Thanks all.
dev
Thanks Andrea for the reply. I am using T-SQL commands right now to backup and restore database. If I use sql-dmo to trap progress event then would that mean that I will have to change the backup/restore sourcecode also to use sql-dmo. Please confirm.
Thanks
|||hi,
"dev" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:8CD41CBC-6EF7-46F8-BC3C-3415F14A6BD5@.microsoft.com...
> Thanks Andrea for the reply. I am using T-SQL commands right now to
backup
>and restore database. If I use sql-dmo to trap progress event then would
that
>mean that I will have to change the backup/restore sourcecode also to use
>sql-dmo. Please confirm.
yep.. you have to use the SQL-DMO backup object to trap the raised events...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||oh no.. so what is this sql-dmo. What is the purpose of it's existance. Why do we need it (besides for the progress bar). How is it different from programming with T-SQL. How can we choose which way to go, T-SQL or SQL-DMO. What are it's advantages an
d disadvantages.
Thanks
|||Also was it unwise of me to opt for T-SQL for doing everything instead of going for DMO. And is it ok to use DMO for backup/restore and use T-SQL for everything else. What are your recommendations.
We are as before an ISV, app will be deployed using MSDE, will have max a couple of databases. Will provide an interface to the user to backup and restore database. Will creare database from app and do version checks for database.
What should we do... or should we wait for SMO..
Thanks for your valuable time.
|||hi,
"dev" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:07DA4684-529D-48D5-9D6A-56DDFDB077A7@.microsoft.com...
> oh no.. so what is this sql-dmo. What is the purpose of it's existance.
Why do we need it
>(besides for the progress bar). How is it different from programming with
T-SQL. How can
> we choose which way to go, T-SQL or SQL-DMO. What are it's advantages and
disadvantages.
> Thanks
SQL-DMO is an acronym for SQL Distributed Management Object and is a full
object model to manage and administer SQL Server..
it exposes a nice object model you can navigate to perform quiet all
management tasks on SQL Server..
it's not designed for data manipulation even if it provides some features
to.
it comes with MSDE and/or can be installed from the Client Tools
installation package of SQL Server.
it is not provided as a separate download and/or package, so you have to
depoly it yourself in MSDE scenarios (you are legitimate to) ... this can be
count as a disadvantage too :-)
it's a little buggy =;-) and eats a lot of memory, but is very handy for
some admin scenario...
Transact-SQL, on the contrary, is the language SQL Server better understand,
and can perform both data manipulation and administration tasks... it's a
separate language where DMO is just a COM object model you can use in any
COM compliant client, so they can not be compared... you shoul'd stick with
Transact-SQL, and use DMO where and when appropriated...
by the way... there's only 1 book worth reading about SQL-DMO, by SQL Server
MVPs Allan Mitchell and Mark Allison,
http://www.compman.co.uk/cgi-win/browse.exe?ref=552118 , which I personally
recommend reading...
FWIW, you can have a look at a free prj of mine at the link following my
sign to have an idea aboout what you can do with SQL-DMO, a prj that
provides a user interface similar to Enteprise Manager written in VB6
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi,
"dev" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:AF907AC5-9610-41F9-95DD-FC68828844F6@.microsoft.com...
> Also was it unwise of me to opt for T-SQL for doing everything instead of
going for DMO.
>And is it ok to use DMO for backup/restore and use T-SQL for everything
else. What are your
>recommendations.
> We are as before an ISV, app will be deployed using MSDE, will have max a
couple of
>databases. Will provide an interface to the user to backup and restore
database.
>Will creare database from app and do version checks for database.
> What should we do... or should we wait for SMO..
if you only need DMO for presenting a progress bar indicating backup
progress, let it be...
you have to talk to SQL Server via Transact-SQL...
perform backup via ADO.Net commands...
SMO will be only available wit SQL Server 2005, and anyway I don't think it
shoul'd be used for traditional programming, but for the same things now
covered by DMO...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea for the insight. I already use your tool since quiet some time and appreciate it. So do you recommend I use T-SQL for everything as now, you know db creation, data manipulation and use dmo for backup/restore which I can later port to use s
mo when yukon arrives..
dev
|||I am sorry Andrea but I didn't understand what you said here:
"if you only need DMO for presenting a progress bar indicating backup
progress, let it be...
you have to talk to SQL Server via Transact-SQL...
perform backup via ADO.Net commands..."
Do you mean that I use T-SQL for everything else and just use DMO for the backup/restore.
Sorry to bother you like this but Thanks
|||hi,
"dev" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:778938C6-1142-4954-B633-BBF0669342D3@.microsoft.com...
> I am sorry Andrea but I didn't understand what you said here:
> "if you only need DMO for presenting a progress bar indicating backup
> progress, let it be...
> you have to talk to SQL Server via Transact-SQL...
> perform backup via ADO.Net commands..."
> Do you mean that I use T-SQL for everything else and just use DMO for the
backup/restore.
> Sorry to bother you like this but Thanks
please excuse my poor english...
what I mean is go with Transact-SQL for all you stuffs, including
Backup/Restore, if you only need SQL-DMO for providing a progress
indicator...
if you need SQL-DMO for other things, then you can consider adding it to
your project references [and setup package :-( ]
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Backuping up Remote Databases
Hello,
I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
pc's in the plant. I make daily backups on the server of the databases.
The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
back up these databases from my central server. Each of the clients
are(should be) setup alike. So, with my job I would need to maybe zip these
files into a file so I know which machine it came from. For example after I
backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
Any suggestions?
Thanks,
Brian
That would require some programming. I'd look into the DMO programming API (SMO if you are on 2005).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Brian Shafer" <BrianShafer@.discussions.microsoft.com> wrote in message
news:72F32CDD-C790-4B2C-AE45-7AF2D5083BB7@.microsoft.com...
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip these
> files into a file so I know which machine it came from. For example after I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
> Any suggestions?
> Thanks,
> Brian
|||Brian Shafer wrote:
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip these
> files into a file so I know which machine it came from. For example after I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
> Any suggestions?
> Thanks,
> Brian
You could try something like this:
Create a stored procedure on each remote instance to backup the databases using T-SQL commands.
Link the remote instances to your central server.
Create DTS packages on your central server to run the stored procedures on the remote instances and then FTP their
resulting backup files to some other server.
I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
pc's in the plant. I make daily backups on the server of the databases.
The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
back up these databases from my central server. Each of the clients
are(should be) setup alike. So, with my job I would need to maybe zip these
files into a file so I know which machine it came from. For example after I
backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
Any suggestions?
Thanks,
Brian
That would require some programming. I'd look into the DMO programming API (SMO if you are on 2005).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Brian Shafer" <BrianShafer@.discussions.microsoft.com> wrote in message
news:72F32CDD-C790-4B2C-AE45-7AF2D5083BB7@.microsoft.com...
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip these
> files into a file so I know which machine it came from. For example after I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
> Any suggestions?
> Thanks,
> Brian
|||Brian Shafer wrote:
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip these
> files into a file so I know which machine it came from. For example after I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
> Any suggestions?
> Thanks,
> Brian
You could try something like this:
Create a stored procedure on each remote instance to backup the databases using T-SQL commands.
Link the remote instances to your central server.
Create DTS packages on your central server to run the stored procedures on the remote instances and then FTP their
resulting backup files to some other server.
Backuping up Remote Databases
Hello,
I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
pc's in the plant. I make daily backups on the server of the databases.
The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
back up these databases from my central server. Each of the clients
are(should be) setup alike. So, with my job I would need to maybe zip these
files into a file so I know which machine it came from. For example after I
backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
Any suggestions?
Thanks,
BrianThat would require some programming. I'd look into the DMO programming API (SMO if you are on 2005).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Brian Shafer" <BrianShafer@.discussions.microsoft.com> wrote in message
news:72F32CDD-C790-4B2C-AE45-7AF2D5083BB7@.microsoft.com...
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip these
> files into a file so I know which machine it came from. For example after I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
> Any suggestions?
> Thanks,
> Brian|||Brian Shafer wrote:
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip these
> files into a file so I know which machine it came from. For example after I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
> Any suggestions?
> Thanks,
> Brian
You could try something like this:
Create a stored procedure on each remote instance to backup the databases using T-SQL commands.
Link the remote instances to your central server.
Create DTS packages on your central server to run the stored procedures on the remote instances and then FTP their
resulting backup files to some other server.
I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
pc's in the plant. I make daily backups on the server of the databases.
The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
back up these databases from my central server. Each of the clients
are(should be) setup alike. So, with my job I would need to maybe zip these
files into a file so I know which machine it came from. For example after I
backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
Any suggestions?
Thanks,
BrianThat would require some programming. I'd look into the DMO programming API (SMO if you are on 2005).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Brian Shafer" <BrianShafer@.discussions.microsoft.com> wrote in message
news:72F32CDD-C790-4B2C-AE45-7AF2D5083BB7@.microsoft.com...
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip these
> files into a file so I know which machine it came from. For example after I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
> Any suggestions?
> Thanks,
> Brian|||Brian Shafer wrote:
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Can I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip these
> files into a file so I know which machine it came from. For example after I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
> Any suggestions?
> Thanks,
> Brian
You could try something like this:
Create a stored procedure on each remote instance to backup the databases using T-SQL commands.
Link the remote instances to your central server.
Create DTS packages on your central server to run the stored procedures on the remote instances and then FTP their
resulting backup files to some other server.
Backuping up Remote Databases
Hello,
I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
pc's in the plant. I make daily backups on the server of the databases.
The SQL databases on the pc's(I'll call clients) don't run sql agent. Can
I
back up these databases from my central server. Each of the clients
are(should be) setup alike. So, with my job I would need to maybe zip these
files into a file so I know which machine it came from. For example after I
backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
Any suggestions?
Thanks,
BrianThat would require some programming. I'd look into the DMO programming API (
SMO if you are on 2005).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Brian Shafer" <BrianShafer@.discussions.microsoft.com> wrote in message
news:72F32CDD-C790-4B2C-AE45-7AF2D5083BB7@.microsoft.com...
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Ca
n I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip the
se
> files into a file so I know which machine it came from. For example after
I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3
.
> Any suggestions?
> Thanks,
> Brian|||Brian Shafer wrote:
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Ca
n I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip the
se
> files into a file so I know which machine it came from. For example after
I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3
.
> Any suggestions?
> Thanks,
> Brian
You could try something like this:
Create a stored procedure on each remote instance to backup the databases us
ing T-SQL commands.
Link the remote instances to your central server.
Create DTS packages on your central server to run the stored procedures on t
he remote instances and then FTP their
resulting backup files to some other server.
I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
pc's in the plant. I make daily backups on the server of the databases.
The SQL databases on the pc's(I'll call clients) don't run sql agent. Can
I
back up these databases from my central server. Each of the clients
are(should be) setup alike. So, with my job I would need to maybe zip these
files into a file so I know which machine it came from. For example after I
backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3.
Any suggestions?
Thanks,
BrianThat would require some programming. I'd look into the DMO programming API (
SMO if you are on 2005).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Brian Shafer" <BrianShafer@.discussions.microsoft.com> wrote in message
news:72F32CDD-C790-4B2C-AE45-7AF2D5083BB7@.microsoft.com...
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Ca
n I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip the
se
> files into a file so I know which machine it came from. For example after
I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3
.
> Any suggestions?
> Thanks,
> Brian|||Brian Shafer wrote:
> Hello,
> I have one SQL Server on a server. and 3 other (?MSDE?)SQL Databases on
> pc's in the plant. I make daily backups on the server of the databases.
> The SQL databases on the pc's(I'll call clients) don't run sql agent. Ca
n I
> back up these databases from my central server. Each of the clients
> are(should be) setup alike. So, with my job I would need to maybe zip the
se
> files into a file so I know which machine it came from. For example after
I
> backup the master, msdb,and user DB, zip into a file called, pc1, pc2, pc3
.
> Any suggestions?
> Thanks,
> Brian
You could try something like this:
Create a stored procedure on each remote instance to backup the databases us
ing T-SQL commands.
Link the remote instances to your central server.
Create DTS packages on your central server to run the stored procedures on t
he remote instances and then FTP their
resulting backup files to some other server.
Backup/Restore Versus Detach/Attach
Hi All,
when I've to deploy my applications (c# and MSDE), generally I make a backup
on th edevelopment machine of the SQL Database the on the deployment machine
I make a restore and restoring from the backup I get my database up and
running (so boiring that I've to change the data/log file path at any
restore...).
Are there any real differences if instead of backup/restore I detach the
database file from the development machine (running sql developer edition)
then copy the file on the deployment machine and then make an attach to that
file?
which one is the best way?
Thanks, Davide.
Davide Piras
Naxo Software
hi Davide,
Davide Piras wrote:
> Hi All,
> when I've to deploy my applications (c# and MSDE), generally I make a
> backup on th edevelopment machine of the SQL Database the on the
> deployment machine I make a restore and restoring from the backup I
> get my database up and running (so boiring that I've to change the
> data/log file path at any restore...).
> Are there any real differences if instead of backup/restore I detach
> the database file from the development machine (running sql developer
> edition) then copy the file on the deployment machine and then make
> an attach to that file?
> which one is the best way?
please remember to add the log file to your distribution too, as it's part
of the dabase files set... and reattaching without the log file can end in
attaching problems...
the restore scenario only requires a little more physical space as you have
to consider the backup size in addition to the database files size...
both scenarios are simple to run but you have to consider some potential
issues..
MSDE usually set the "autoclose" database property, where the full blown SQL
Server editions do not, so you'll end up with a database that does not
reflect this standard MSDE setting, but it could be a choice...
you do not inherit database settings/options/objects from the end user model
database but from yours...
this can bring up some problems regarding orphaned users you will have to
fix by use of the sp_change_users_login system stored procedure
(http://msdn.microsoft.com/library/de...ca-cz_8qzy.asp
, http://www.sqlservercentral.com/colu...okenlogins.asp )
personally I go this way, http://tinyurl.com/dyjjg , that will even help in
structure upgrade to, and can grant a database deployment based on version
control check ... and the best article I found for this kind of situation is
http://msdn.microsoft.com/msdnmag/is...baseinstaller/
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Ciao Andrea,
thanks for you help, I will read those articles BEFORE the next deployment
loop...
you know I use your DbaManager 0.12.0 as a Client User Interface?! :-)
Nice and useful Tool, thanks!
Davide.
when I've to deploy my applications (c# and MSDE), generally I make a backup
on th edevelopment machine of the SQL Database the on the deployment machine
I make a restore and restoring from the backup I get my database up and
running (so boiring that I've to change the data/log file path at any
restore...).
Are there any real differences if instead of backup/restore I detach the
database file from the development machine (running sql developer edition)
then copy the file on the deployment machine and then make an attach to that
file?
which one is the best way?
Thanks, Davide.
Davide Piras
Naxo Software
hi Davide,
Davide Piras wrote:
> Hi All,
> when I've to deploy my applications (c# and MSDE), generally I make a
> backup on th edevelopment machine of the SQL Database the on the
> deployment machine I make a restore and restoring from the backup I
> get my database up and running (so boiring that I've to change the
> data/log file path at any restore...).
> Are there any real differences if instead of backup/restore I detach
> the database file from the development machine (running sql developer
> edition) then copy the file on the deployment machine and then make
> an attach to that file?
> which one is the best way?
please remember to add the log file to your distribution too, as it's part
of the dabase files set... and reattaching without the log file can end in
attaching problems...
the restore scenario only requires a little more physical space as you have
to consider the backup size in addition to the database files size...
both scenarios are simple to run but you have to consider some potential
issues..
MSDE usually set the "autoclose" database property, where the full blown SQL
Server editions do not, so you'll end up with a database that does not
reflect this standard MSDE setting, but it could be a choice...
you do not inherit database settings/options/objects from the end user model
database but from yours...
this can bring up some problems regarding orphaned users you will have to
fix by use of the sp_change_users_login system stored procedure
(http://msdn.microsoft.com/library/de...ca-cz_8qzy.asp
, http://www.sqlservercentral.com/colu...okenlogins.asp )
personally I go this way, http://tinyurl.com/dyjjg , that will even help in
structure upgrade to, and can grant a database deployment based on version
control check ... and the best article I found for this kind of situation is
http://msdn.microsoft.com/msdnmag/is...baseinstaller/
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Ciao Andrea,
thanks for you help, I will read those articles BEFORE the next deployment
loop...
you know I use your DbaManager 0.12.0 as a Client User Interface?! :-)
Nice and useful Tool, thanks!
Davide.
Sunday, February 19, 2012
Backup/Restore from MSDE 1.0 to MSDE 2000
To anyone who can assist:
Everything I have read online today states that I should be able to take a
backup copy of my database in MSDE 1.0 and restore it to MSDE 2000. However,
I am experiencing problems with this. We are wanting to upgrade our customer
sites to MSDE 2000 (from MSDE 1.0), and we have as part of our product a
utility which they can backup and restore their databases.
The Backup utility calls this statement:
BACKUP DATABASE dbName TO DISK = fileName WITH BLOCKSIZE=2048
The Restore utility calls this statement:
RESTORE DATABASE dbName FROM DISK = fileName WITH REPLACE
I am able to uninstall MSDE 1.0 from our server, install MSDE 2000, copy our
DB (mdf & ldf files) from the original location to the Data directory for
MSDE 2000, and attach to the database. Everything works great until I
attempt to restore a copy of the database that was generated in MSDE 1.0.
Our Restore utility stops our Database server service, runs the RESTORE
command, then attempts to restart our DB service. This fails, and when I
attempt to look at the database in DbaMgr2K (a very nice tool, BTW), I
receive an error message stating that I need to upgrade this database.
Is there something I am overlooking? The only thing seems to be different
between the two installations is that we had to change our ODBC
configuration. Using MSDE 1.0, we could connect to the "SQL Server"
connection. Using MSDE 2000, we had to change this to our local server.
Thanks in advance for your help!
Becky
hi Becky,
BElders wrote:
> ...
> I am able to uninstall MSDE 1.0 from our server, install MSDE 2000,
> copy our DB (mdf & ldf files) from the original location to the Data
> directory for MSDE 2000, and attach to the database. Everything
> works great until I attempt to restore a copy of the database that
> was generated in MSDE 1.0. Our Restore utility stops our Database
> server service, runs the RESTORE command, then attempts to restart
> our DB service. This fails, and when I attempt to look at the
> database in DbaMgr2K (a very nice tool, BTW), I receive an error
> message stating that I need to upgrade this database.
it's not clear to me why are you stopping the service... if you stop it, how
do you perform the RESTORE operation?
the service of the restoring server must be running to do that , but
probably I misunderstood your words.. or this is can be the cause of the
restore operation failing...
restoring the MSDE 1.0 database on a MSDE 2000 instance will upgrade it to
2000 version, including the te database compatibility level, and DbaMgr2k
and DbaMgr are engine version specefic and not database version (thank you
for your interest in these prjs of mine), so you have to use DbaMgr2k for
MSDE 2000 instances, and DbaMgr for MSDE 1.0 instances..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Just to clear up the confusion...I am not stopping the SQL server service
when using our Restore utility. The service I mentioned is part of our
product, and this is really performed as a precaution. Also, the Restore
command appears to execute OK. The error occurs when our service is
attempting to restart.
That being said, I decided to play around with the Backup/Restore operations
within DbaMgr2k (I am pretty new at using the tool). I received an error
message when trying to run the Restore using the old copy because it could
not locate the mssql7\data directory (removed - by me - as part of the
uninstall of MSDE 1.0). I added this directory back, and the RESTORE
functioned correctly. One thing that I did not realize was that the MDF/LDF
files are relocated in this process. I attempted to mimic this using our
Restore utility, but the same error occurred.
My conclusion is that it looks as though the RESTORE statement in our
utility is not "robust" enough. So I am going to either have to modify our
utility, or just provide instructions to our clients of the steps needed to
perform the same operations using DbaMgr2K (I think I like the latter
solution
.
Thanks for your help!!
Becky
Everything I have read online today states that I should be able to take a
backup copy of my database in MSDE 1.0 and restore it to MSDE 2000. However,
I am experiencing problems with this. We are wanting to upgrade our customer
sites to MSDE 2000 (from MSDE 1.0), and we have as part of our product a
utility which they can backup and restore their databases.
The Backup utility calls this statement:
BACKUP DATABASE dbName TO DISK = fileName WITH BLOCKSIZE=2048
The Restore utility calls this statement:
RESTORE DATABASE dbName FROM DISK = fileName WITH REPLACE
I am able to uninstall MSDE 1.0 from our server, install MSDE 2000, copy our
DB (mdf & ldf files) from the original location to the Data directory for
MSDE 2000, and attach to the database. Everything works great until I
attempt to restore a copy of the database that was generated in MSDE 1.0.
Our Restore utility stops our Database server service, runs the RESTORE
command, then attempts to restart our DB service. This fails, and when I
attempt to look at the database in DbaMgr2K (a very nice tool, BTW), I
receive an error message stating that I need to upgrade this database.
Is there something I am overlooking? The only thing seems to be different
between the two installations is that we had to change our ODBC
configuration. Using MSDE 1.0, we could connect to the "SQL Server"
connection. Using MSDE 2000, we had to change this to our local server.
Thanks in advance for your help!
Becky
hi Becky,
BElders wrote:
> ...
> I am able to uninstall MSDE 1.0 from our server, install MSDE 2000,
> copy our DB (mdf & ldf files) from the original location to the Data
> directory for MSDE 2000, and attach to the database. Everything
> works great until I attempt to restore a copy of the database that
> was generated in MSDE 1.0. Our Restore utility stops our Database
> server service, runs the RESTORE command, then attempts to restart
> our DB service. This fails, and when I attempt to look at the
> database in DbaMgr2K (a very nice tool, BTW), I receive an error
> message stating that I need to upgrade this database.
it's not clear to me why are you stopping the service... if you stop it, how
do you perform the RESTORE operation?
the service of the restoring server must be running to do that , but
probably I misunderstood your words.. or this is can be the cause of the
restore operation failing...
restoring the MSDE 1.0 database on a MSDE 2000 instance will upgrade it to
2000 version, including the te database compatibility level, and DbaMgr2k
and DbaMgr are engine version specefic and not database version (thank you
for your interest in these prjs of mine), so you have to use DbaMgr2k for
MSDE 2000 instances, and DbaMgr for MSDE 1.0 instances..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Just to clear up the confusion...I am not stopping the SQL server service
when using our Restore utility. The service I mentioned is part of our
product, and this is really performed as a precaution. Also, the Restore
command appears to execute OK. The error occurs when our service is
attempting to restart.
That being said, I decided to play around with the Backup/Restore operations
within DbaMgr2k (I am pretty new at using the tool). I received an error
message when trying to run the Restore using the old copy because it could
not locate the mssql7\data directory (removed - by me - as part of the
uninstall of MSDE 1.0). I added this directory back, and the RESTORE
functioned correctly. One thing that I did not realize was that the MDF/LDF
files are relocated in this process. I attempted to mimic this using our
Restore utility, but the same error occurred.
My conclusion is that it looks as though the RESTORE statement in our
utility is not "robust" enough. So I am going to either have to modify our
utility, or just provide instructions to our clients of the steps needed to
perform the same operations using DbaMgr2K (I think I like the latter
solution
.Thanks for your help!!
Becky
Subscribe to:
Posts (Atom)