I need a better installation procedure for my software, so I wanted to merge
the MSDE install into the main one. At the moment the Setup has been built
by a third part developer, who use Installshiled.
Problem is, he doesn't know which version of Installshield he needs. Someone
can give me a hint?
On Thu, 1 Jul 2004 16:18:40 +0200, Drizzt <drizzt.du@.libero.it> wrote:
> I need a better installation procedure for my software, so I wanted to
> merge
> the MSDE install into the main one. At the moment the Setup has been
> built
> by a third part developer, who use Installshiled.
> Problem is, he doesn't know which version of Installshield he needs.
> Someone can give me a hint?
From what I read, InstallShield 7 should be alright; maybe even 6.
Not related to MSDE, I am struggling with it, though: I am unable to
create simple Upgrade packages that replace a couple of files in an
installation. something that InnoSetup and InstallShield 5 do perfectly
well.
Stefan
|||When I last spoke to them, the installshield guys didn't have the bootstrapper out for MSDE. They still had the merge modules but be warned microsoft does not want you to continue that route. I even spoke with WISE Solutions and they also mentioned that
they were working on replacing the merge module for MSDE.. so something to keep in mind.
Thanks
dev
"Stefan M. Huber" wrote:
> On Thu, 1 Jul 2004 16:18:40 +0200, Drizzt <drizzt.du@.libero.it> wrote:
>
> From what I read, InstallShield 7 should be alright; maybe even 6.
> Not related to MSDE, I am struggling with it, though: I am unable to
> create simple Upgrade packages that replace a couple of files in an
> installation. something that InnoSetup and InstallShield 5 do perfectly
> well.
> Stefan
>
|||"dev_kh" <devkh@.discussions.microsoft.com> ha scritto nel messaggio
news:3014BFB6-1C09-49FB-BA4E-C21475CDD808@.microsoft.com...
> When I last spoke to them, the installshield guys didn't
> have the bootstrapper out for MSDE. They still had the merge
> modules but be warned microsoft does not want you to continue
> that route. I even spoke with WISE Solutions and they also mentioned
> that they were working on replacing the merge module for MSDE.. so
something to keep in mind.
Sorry, I got lost.
Our product must be a self-easy-installing one. I have no experience about
Installations packages, and the (external)guy who must build it needs
directions from me, as he have never installed MSDE before.
We need a tight integration between the two -installshield and MSDE- 'cause
in case of errors we need the installation to halt and report the error,
while now it simply goes on...
So, is there a simply solution? What are the methods commonly used for this?
Sorry to bother, but I really have no clues...
|||| So, is there a simply solution? What are the methods commonly used for this?
I plan on using InnoSetup. I have been using it for over a year - love it. I
have not used it for MSDE, but I plan to.
<quote>
Yes, we now know how to. But it has taken a *LOT* of effort to
integrate it into InnoSetup in such a way that it:
* Checks the existence of an earlier MSDE installation
* If found check if it was done from our software
* If not, install a new instance using Microsoft setup
* Make sure to use the correct MSI file during install
* Make sure to set all install parameters correct
* Start the MSDE after install
* Connect to MSDE and install database
* Make sure it works on all NT platforms (big problems on NT4)
* etc etc etc
We have probably spent one man-moth on this task alone... Bo
</quote>
http://fox.wikis.com/wc.dll?Wiki~Inn...ScriptMSDE~VFP
Carl K
|||So, do you have a workable solution for installing an app and MSDE or not?
TIA,
Paul
"Carl Karsten" <carl@.personnelware.com> wrote in message
news:%23dnKozoYEHA.3988@.tk2msftngp13.phx.gbl...
> | So, is there a simply solution? What are the methods commonly used for
this?
> I plan on using InnoSetup. I have been using it for over a year - love
it. I
> have not used it for MSDE, but I plan to.
> <quote>
> Yes, we now know how to. But it has taken a *LOT* of effort to
> integrate it into InnoSetup in such a way that it:
> * Checks the existence of an earlier MSDE installation
> * If found check if it was done from our software
> * If not, install a new instance using Microsoft setup
> * Make sure to use the correct MSI file during install
> * Make sure to set all install parameters correct
> * Start the MSDE after install
> * Connect to MSDE and install database
> * Make sure it works on all NT platforms (big problems on NT4)
> * etc etc etc
> We have probably spent one man-moth on this task alone... Bo
> </quote>
> http://fox.wikis.com/wc.dll?Wiki~Inn...ScriptMSDE~VFP
> Carl K
>
|||Personally, no.
If the Inno guys say it will fly, I have no reason to doubt them. They aren't
trying to sell me something - the beauty of open source software.
Carl K
"Paul McTeigue" <paul_mcteigue@.msn.com> wrote in message
news:%23vGPGesYEHA.2816@.TK2MSFTNGP11.phx.gbl...
| So, do you have a workable solution for installing an app and MSDE or not?
|
| TIA,
| Paul
|
| "Carl Karsten" <carl@.personnelware.com> wrote in message
| news:%23dnKozoYEHA.3988@.tk2msftngp13.phx.gbl...
| >
| > | So, is there a simply solution? What are the methods commonly used for
| this?
| >
| > I plan on using InnoSetup. I have been using it for over a year - love
| it. I
| > have not used it for MSDE, but I plan to.
| >
| > <quote>
| > Yes, we now know how to. But it has taken a *LOT* of effort to
| > integrate it into InnoSetup in such a way that it:
| > * Checks the existence of an earlier MSDE installation
| > * If found check if it was done from our software
| > * If not, install a new instance using Microsoft setup
| > * Make sure to use the correct MSI file during install
| > * Make sure to set all install parameters correct
| > * Start the MSDE after install
| > * Connect to MSDE and install database
| > * Make sure it works on all NT platforms (big problems on NT4)
| > * etc etc etc
| >
| > We have probably spent one man-moth on this task alone... Bo
| > </quote>
| >
| > http://fox.wikis.com/wc.dll?Wiki~Inn...ScriptMSDE~VFP
| >
| > Carl K
| >
|
|
sql
Showing posts with label software. Show all posts
Showing posts with label software. Show all posts
Friday, March 30, 2012
MSDE Alternative
My company develops software that is distributed to thousands of customers. We chose MSDE as the database engine. Over the past 4 months, we have spent countless hours with customers, Microsoft, Installshield and web searches trying to resolve issues with installing MSDE. The issues seem to vary by customer and most take a great deal of support time. We understood MSDE to be a product that requires little support but in hindsight, it appears that it requires a great deal of knowledge just to get installed. We make small steps but no leaps forward.
It has come time to evaluate other products. If there is a magic bullet, I would love to hear about it. In its absence, does anyone have success to share with other products?
PhilWhen you install MSDE, be sure to also install the latest MDAC update (2.8 now I think).
I had similar problems distributing testing software to universities - a total nightmare. Insisting on the latest MDAC for all servers and clients helped tremendously.
After that, it was convincing admins to assign the proper privledges, which was akin to pulling teeth.|||Thank you for your response. Below is a list of solutions we have tried. These are the items that have at least helped. We have tried others with no success.
- Updated MDAC to most current version
- Modified the install to use MS Setup instead of Installshield Merge Modules
- Installed outside of the Installshield product
- Ensured that Print/File Sharing is installed and enabled
- Copied the contents from the CD to the hard drive and installed
- Installed MSDE with blank SA password and then changed it manually after installation
- Verified that no previous instance of MSDE or SQL Server is installed
I may have missed a couple but these give you an idea of what we have been through. We sell an inexpensive product and the product has to install without event.
Any help is greatly appreciated.
Phil|||First, let me say I have no good recommendations for you as alternatives.
I am curious as to what kinds of problems you are seeing.
Have you tried a full SQL Server install in any of the trouble spots to see if would eliviate the problems?
Our biggest problems almost always stemmed from NT permissions, once the MDAC issues were ironed out.|||Our experience falls into three major categories. First, we have customers who get to the end of the MSDE Install and it starts rolling back and will never complete and ends up leaving a mess. Next, we have customers whose install freezes in the middle of the install and they have to reboot to recover. Lastly, we have customers who appear to be installed correctly but are not able to connect to the MSDE engine.
We have also wrestled with the admin issues you talk about. However, those are generally fairly quick support calls and get resolution.
Phil|||We're just discussing the install of MSDE?
What if they have it installed already?
Does your application install it for them?
Do you do a restore of a dump?|||Have you designed your own installation of MSDE, or are you using Microsoft's installer?|||Yes, we are trying to install MSDE. Initially, we tried installing via Installshield merge modules. In late fall, at Microsoft's direction, we broke our install into three pieces. We install .NET, then MSDE (using Microsoft's installer), and then lastly our custom software. We have no problems with the components other than MSDE. If MSDE is already installed, it doesn't appear to cause issues. However, some suggested that we should clean up any prior versions. We tried that as an option with very limited success.
If I understand the restore question, we are starting from scratch.|||Sounds like the problem is Microsoft's, if it is their installer that is failing. Not much consolation, but what do they say?|||Over the past few days, we have talked to Microsoft a number of times. They are attempting to give us help at chipping away at the issues. However, they have also indicated that MSDE is closer to full SQL server than it is to a "personal" database (which was the way we interpreted much of their promotional information) for the purposes of the installation discussion.
We are working with them to try to resolve as many issues as possible and hope to build an installation to reflect that information. In the meantime, we are still investigating other alternatives. Our product stretches a bit outside the standalone environment into some network configurations. I am looking for a product that is easy to install but can go into a "light" network environment without introducing corruption.
Any ideas?|||Man, I can't tell you how much I hate saying this, but Access might actually work for you, if it is cheifly a standalone app, with occational (limited concurrent users) network use. I am dodging lightning bolts here.
Also, it is (was?) my understanding that MS planned on ditching Access/Jet for the desktop, and replace it with Access/MSDE. Are they backing off that concept now?
Plus, desktop or not, the they should (need) to get the thing to actually install without rolling itself back.
Hmm, just a thought. Could it be related in any way to XP config save points?|||Hi,
Just wanting to find out if there were any breakthroughs in consistently installing MSDE?
My company has had similar problems to what Phil described in this thread.
We've also tried all sorts of variations. Ensuring MDAC 2.8 and IE 6(!) is installed first made helped, but we still get a significant proportion of failed installs.
As with Phil, we can't afford to spend hours working with each customer to make the install work. MSDE is used with the low end (cheap) version of our software!
Regards,
Peter|||hi, i've encountered such problem dealing with MSDE installation and deployment on such environment you said. why not try the full scale MS SQL Server? 2000 i recommened 'coz it solve the problem. Another thing is i'm trying another db, (MySQL, InterBase, Adabas D and MaxDB) which are good alternatives for MSDE. but if you prefer Microsoft products, go to the full scale MS SQL Server. that should solve your problem in any ways. Hard to find that "lite" db. :(|||Full SQL2K instead of MSDE? You may degrade your workstation if you go that route. Reading MSDE prerequisites definitely gets you closer to performing a successful install.
It has come time to evaluate other products. If there is a magic bullet, I would love to hear about it. In its absence, does anyone have success to share with other products?
PhilWhen you install MSDE, be sure to also install the latest MDAC update (2.8 now I think).
I had similar problems distributing testing software to universities - a total nightmare. Insisting on the latest MDAC for all servers and clients helped tremendously.
After that, it was convincing admins to assign the proper privledges, which was akin to pulling teeth.|||Thank you for your response. Below is a list of solutions we have tried. These are the items that have at least helped. We have tried others with no success.
- Updated MDAC to most current version
- Modified the install to use MS Setup instead of Installshield Merge Modules
- Installed outside of the Installshield product
- Ensured that Print/File Sharing is installed and enabled
- Copied the contents from the CD to the hard drive and installed
- Installed MSDE with blank SA password and then changed it manually after installation
- Verified that no previous instance of MSDE or SQL Server is installed
I may have missed a couple but these give you an idea of what we have been through. We sell an inexpensive product and the product has to install without event.
Any help is greatly appreciated.
Phil|||First, let me say I have no good recommendations for you as alternatives.
I am curious as to what kinds of problems you are seeing.
Have you tried a full SQL Server install in any of the trouble spots to see if would eliviate the problems?
Our biggest problems almost always stemmed from NT permissions, once the MDAC issues were ironed out.|||Our experience falls into three major categories. First, we have customers who get to the end of the MSDE Install and it starts rolling back and will never complete and ends up leaving a mess. Next, we have customers whose install freezes in the middle of the install and they have to reboot to recover. Lastly, we have customers who appear to be installed correctly but are not able to connect to the MSDE engine.
We have also wrestled with the admin issues you talk about. However, those are generally fairly quick support calls and get resolution.
Phil|||We're just discussing the install of MSDE?
What if they have it installed already?
Does your application install it for them?
Do you do a restore of a dump?|||Have you designed your own installation of MSDE, or are you using Microsoft's installer?|||Yes, we are trying to install MSDE. Initially, we tried installing via Installshield merge modules. In late fall, at Microsoft's direction, we broke our install into three pieces. We install .NET, then MSDE (using Microsoft's installer), and then lastly our custom software. We have no problems with the components other than MSDE. If MSDE is already installed, it doesn't appear to cause issues. However, some suggested that we should clean up any prior versions. We tried that as an option with very limited success.
If I understand the restore question, we are starting from scratch.|||Sounds like the problem is Microsoft's, if it is their installer that is failing. Not much consolation, but what do they say?|||Over the past few days, we have talked to Microsoft a number of times. They are attempting to give us help at chipping away at the issues. However, they have also indicated that MSDE is closer to full SQL server than it is to a "personal" database (which was the way we interpreted much of their promotional information) for the purposes of the installation discussion.
We are working with them to try to resolve as many issues as possible and hope to build an installation to reflect that information. In the meantime, we are still investigating other alternatives. Our product stretches a bit outside the standalone environment into some network configurations. I am looking for a product that is easy to install but can go into a "light" network environment without introducing corruption.
Any ideas?|||Man, I can't tell you how much I hate saying this, but Access might actually work for you, if it is cheifly a standalone app, with occational (limited concurrent users) network use. I am dodging lightning bolts here.
Also, it is (was?) my understanding that MS planned on ditching Access/Jet for the desktop, and replace it with Access/MSDE. Are they backing off that concept now?
Plus, desktop or not, the they should (need) to get the thing to actually install without rolling itself back.
Hmm, just a thought. Could it be related in any way to XP config save points?|||Hi,
Just wanting to find out if there were any breakthroughs in consistently installing MSDE?
My company has had similar problems to what Phil described in this thread.
We've also tried all sorts of variations. Ensuring MDAC 2.8 and IE 6(!) is installed first made helped, but we still get a significant proportion of failed installs.
As with Phil, we can't afford to spend hours working with each customer to make the install work. MSDE is used with the low end (cheap) version of our software!
Regards,
Peter|||hi, i've encountered such problem dealing with MSDE installation and deployment on such environment you said. why not try the full scale MS SQL Server? 2000 i recommened 'coz it solve the problem. Another thing is i'm trying another db, (MySQL, InterBase, Adabas D and MaxDB) which are good alternatives for MSDE. but if you prefer Microsoft products, go to the full scale MS SQL Server. that should solve your problem in any ways. Hard to find that "lite" db. :(|||Full SQL2K instead of MSDE? You may degrade your workstation if you go that route. Reading MSDE prerequisites definitely gets you closer to performing a successful install.
MSDE 7.0 and SQL2000
Can you install SQL2000 on a server with an application
that is using MSDE 7.0 which was installed with the
software ?
If you can, what is the best way to do so without it
affecting the previous installation of MSDE 7.0 ?Yes you can. BE aware, though, that MDAC on the machine will be upgraded to 2.6 (if not or higher
already), so make sure you test the app for that MDAC version.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Valencia" <vahorda@.hotmail.com> wrote in message news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
> Can you install SQL2000 on a server with an application
> that is using MSDE 7.0 which was installed with the
> software ?
> If you can, what is the best way to do so without it
> affecting the previous installation of MSDE 7.0 ?
>|||Thank you Tibor. I checked the version of MDAC and it is
2.5.
>--Original Message--
>Yes you can. BE aware, though, that MDAC on the machine
will be upgraded to 2.6 (if not or higher
>already), so make sure you test the app for that MDAC
version.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Valencia" <vahorda@.hotmail.com> wrote in message
news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
>> Can you install SQL2000 on a server with an application
>> that is using MSDE 7.0 which was installed with the
>> software ?
>> If you can, what is the best way to do so without it
>> affecting the previous installation of MSDE 7.0 ?
>
>.
>sql
that is using MSDE 7.0 which was installed with the
software ?
If you can, what is the best way to do so without it
affecting the previous installation of MSDE 7.0 ?Yes you can. BE aware, though, that MDAC on the machine will be upgraded to 2.6 (if not or higher
already), so make sure you test the app for that MDAC version.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Valencia" <vahorda@.hotmail.com> wrote in message news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
> Can you install SQL2000 on a server with an application
> that is using MSDE 7.0 which was installed with the
> software ?
> If you can, what is the best way to do so without it
> affecting the previous installation of MSDE 7.0 ?
>|||Thank you Tibor. I checked the version of MDAC and it is
2.5.
>--Original Message--
>Yes you can. BE aware, though, that MDAC on the machine
will be upgraded to 2.6 (if not or higher
>already), so make sure you test the app for that MDAC
version.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Valencia" <vahorda@.hotmail.com> wrote in message
news:a86f01c3ebb2$9d88f350$a401280a@.phx.gbl...
>> Can you install SQL2000 on a server with an application
>> that is using MSDE 7.0 which was installed with the
>> software ?
>> If you can, what is the best way to do so without it
>> affecting the previous installation of MSDE 7.0 ?
>
>.
>sql
Wednesday, March 28, 2012
msde 7
I need to change a computer name on a computer running
msde 7, But i need to do this without doing a reinstall or
update of the software. Any ideas?
With SQL Server 7.0 you cannot rename the computer it is running on without
reinstalling SQL Server. Your best course of action is to install MSDE 2000
on a the same box (or new system) create the logins you need for the
database, restore the database to the new instance of SQL Server and synch
the logins with the database users with sp_change_users_login
Jim
"dhaven" <dhaven@.stny.rr.com> wrote in message
news:2b67601c4683e$7aa10310$a401280a@.phx.gbl...
> I need to change a computer name on a computer running
> msde 7, But i need to do this without doing a reinstall or
> update of the software. Any ideas?
msde 7, But i need to do this without doing a reinstall or
update of the software. Any ideas?
With SQL Server 7.0 you cannot rename the computer it is running on without
reinstalling SQL Server. Your best course of action is to install MSDE 2000
on a the same box (or new system) create the logins you need for the
database, restore the database to the new instance of SQL Server and synch
the logins with the database users with sp_change_users_login
Jim
"dhaven" <dhaven@.stny.rr.com> wrote in message
news:2b67601c4683e$7aa10310$a401280a@.phx.gbl...
> I need to change a computer name on a computer running
> msde 7, But i need to do this without doing a reinstall or
> update of the software. Any ideas?
Monday, March 26, 2012
MSDE 2000 redistribution rights
Hi,
I am trying to find out which parts of MSDE 2000 I can redistribute
with my software. Specifically, I am trying to determine if I can
redistribute the entire MSDE2000 package i.e. MSDE2000A.exe
The EULA for MSDE (found at
http://www.microsoft.com/sql/msde/ho...stregister.asp) states
the following:
"2.ADDITIONAL LICENSE RIGHTS -- REDISTRIBUTABLE CODE. In addition to
the rights granted in Section 1, certain portions of the Software, as
described in this Section 2, are provided to you with additional
license rights. These additional license rights are conditioned upon
your compliance with the distribution requirements and license
restrictions described in Section 3. Microsoft grants you a
nonexclusive, royalty-free right to reproduce and distribute the object
code form of any portion of the Software listed in REDIST.TXT
("Redistributable Code"). For general redistribution requirements
for Redistributable Code, see Section 3.1, below."
I have interpreted the above to mean that you can redistribute only
those components listed in REDIST.TXT. So I took at look at REDIST.TXT
(found at
http://download.microsoft.com/downlo...SDE_redist.txt)
However, MSDE2000A.exe is not listed there, only individual components.
So it looks like I am out of luck, but before I give up, I do want to
make sure that I have not misread anything.
So am I allowed to redistribute MSDE2000A.exe or do I have to limit
myself to the components listed in REDIST.TXT? If I can redistribute
MSDE2000A.exe, can someone point me to some documentation from
Microsoft that says that?
Thanks,
- Hiren
hi Hiren,
hirenc wrote:
> Hi,
> I am trying to find out which parts of MSDE 2000 I can redistribute
> with my software. Specifically, I am trying to determine if I can
> redistribute the entire MSDE2000 package i.e. MSDE2000A.exe
as long as you registered (for free) at
http://www.microsoft.com/sql/msde/ho...stregister.asp for
distribution rights, you can include
http://www.microsoft.com/sql/msde/do...s/download.asp package in your
distributions...
enjoy (MSDE)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
Thanks for your response, but that is not what the license agreement
says. If you read the license agreement at the site you register at
(http://www.microsoft.com/sql/msde/ho...stregister.asp), it
specifically mentions that you can only redistribute certain
components. Nowhere in the license agreement does it give you the right
to distribute the entier package. This is clearly stated in the license
agreement you have to agree to when you register.
In fact, even the web page states:
"The Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
redistribution license agreement grants you the right to redistribute
certain components of MSDE 2000 with your software application. For
information about components that can be redistributed with your
software application, see the list of redistributable components."
Note the words "edistribute certain components of MSDE 2000".
Where does it state in the agreement that you can redistribute the
entier package?
- Hiren
|||hi,
hirenc wrote:
> Andrea,
> Thanks for your response, but that is not what the license agreement
> says. If you read the license agreement at the site you register at
> (http://www.microsoft.com/sql/msde/ho...stregister.asp), it
> specifically mentions that you can only redistribute certain
> components. Nowhere in the license agreement does it give you the
> right to distribute the entier package. This is clearly stated in the
> license agreement you have to agree to when you register.
> In fact, even the web page states:
> "The Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
> redistribution license agreement grants you the right to redistribute
> certain components of MSDE 2000 with your software application. For
> information about components that can be redistributed with your
> software application, see the list of redistributable components."
> Note the words "edistribute certain components of MSDE 2000".
> Where does it state in the agreement that you can redistribute the
> entier package?
the package should be distrubuted as a single unit, and you are licensed to,
so that the "components" list is referred to single individual components
distribution... ie: you can redistribute SQL-DMO but not SQL-NS (actually
SQL-NS is included in the redist.txt list, but
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp exclude it) and so
on, and again, only as part of an "application bundle"...
MSDE Rel A is free (to download and use) and has been designed to be usable
by everyone, and registering for distribution enables you to...
ok... this is all "legalese"... but you know... lawyers are there to work
too.. :D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
I am trying to find out which parts of MSDE 2000 I can redistribute
with my software. Specifically, I am trying to determine if I can
redistribute the entire MSDE2000 package i.e. MSDE2000A.exe
The EULA for MSDE (found at
http://www.microsoft.com/sql/msde/ho...stregister.asp) states
the following:
"2.ADDITIONAL LICENSE RIGHTS -- REDISTRIBUTABLE CODE. In addition to
the rights granted in Section 1, certain portions of the Software, as
described in this Section 2, are provided to you with additional
license rights. These additional license rights are conditioned upon
your compliance with the distribution requirements and license
restrictions described in Section 3. Microsoft grants you a
nonexclusive, royalty-free right to reproduce and distribute the object
code form of any portion of the Software listed in REDIST.TXT
("Redistributable Code"). For general redistribution requirements
for Redistributable Code, see Section 3.1, below."
I have interpreted the above to mean that you can redistribute only
those components listed in REDIST.TXT. So I took at look at REDIST.TXT
(found at
http://download.microsoft.com/downlo...SDE_redist.txt)
However, MSDE2000A.exe is not listed there, only individual components.
So it looks like I am out of luck, but before I give up, I do want to
make sure that I have not misread anything.
So am I allowed to redistribute MSDE2000A.exe or do I have to limit
myself to the components listed in REDIST.TXT? If I can redistribute
MSDE2000A.exe, can someone point me to some documentation from
Microsoft that says that?
Thanks,
- Hiren
hi Hiren,
hirenc wrote:
> Hi,
> I am trying to find out which parts of MSDE 2000 I can redistribute
> with my software. Specifically, I am trying to determine if I can
> redistribute the entire MSDE2000 package i.e. MSDE2000A.exe
as long as you registered (for free) at
http://www.microsoft.com/sql/msde/ho...stregister.asp for
distribution rights, you can include
http://www.microsoft.com/sql/msde/do...s/download.asp package in your
distributions...
enjoy (MSDE)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea,
Thanks for your response, but that is not what the license agreement
says. If you read the license agreement at the site you register at
(http://www.microsoft.com/sql/msde/ho...stregister.asp), it
specifically mentions that you can only redistribute certain
components. Nowhere in the license agreement does it give you the right
to distribute the entier package. This is clearly stated in the license
agreement you have to agree to when you register.
In fact, even the web page states:
"The Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
redistribution license agreement grants you the right to redistribute
certain components of MSDE 2000 with your software application. For
information about components that can be redistributed with your
software application, see the list of redistributable components."
Note the words "edistribute certain components of MSDE 2000".
Where does it state in the agreement that you can redistribute the
entier package?
- Hiren
|||hi,
hirenc wrote:
> Andrea,
> Thanks for your response, but that is not what the license agreement
> says. If you read the license agreement at the site you register at
> (http://www.microsoft.com/sql/msde/ho...stregister.asp), it
> specifically mentions that you can only redistribute certain
> components. Nowhere in the license agreement does it give you the
> right to distribute the entier package. This is clearly stated in the
> license agreement you have to agree to when you register.
> In fact, even the web page states:
> "The Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
> redistribution license agreement grants you the right to redistribute
> certain components of MSDE 2000 with your software application. For
> information about components that can be redistributed with your
> software application, see the list of redistributable components."
> Note the words "edistribute certain components of MSDE 2000".
> Where does it state in the agreement that you can redistribute the
> entier package?
the package should be distrubuted as a single unit, and you are licensed to,
so that the "components" list is referred to single individual components
distribution... ie: you can redistribute SQL-DMO but not SQL-NS (actually
SQL-NS is included in the redist.txt list, but
http://www.microsoft.com/sql/msde/howtobuy/msdeuse.asp exclude it) and so
on, and again, only as part of an "application bundle"...
MSDE Rel A is free (to download and use) and has been designed to be usable
by everyone, and registering for distribution enables you to...
ok... this is all "legalese"... but you know... lawyers are there to work
too.. :D
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
MSDE 2000 on XP help...
Hello all, im new here and do not have no experience with sql. I am trying to install a tax software that I need to run my little business. When I install it gets to a popint that it asks me for my SQL server usernme and password. I remember doing this last year and I reinstalled MSDE and set up a username and password. I seem to not remember what I used, i tried all that I would have but can not get past that step.
I remember adding some lines in the setup,ini file when I installed it last year. Now I can go ahead and reinstall it again and set up a new one, but will the uninstalling and reinstalling of MSDE affect my previous software from last year? Its the same software but I need this years installed.
I have tried using sa as the username and a blank password, with a password and others that I have read up on, still cant log on. Keep getting worng credential screen.
Is there a way to get that info, i doubt it or else it would not be secure, or can I just simply reinstall MSDE?
Many thanks!!
Forget MSDE. Use Sql Server Express instead. It's much easier:http://www.microsoft.com/sql/editions/express/default.mspx
|||
If you are going to uninstall and reinstall it again, you will be loosing all the data that is there from the previous year. So if you are ok with that , you can go ahead and reinstall it.
Also, since you are using a application, the application needs to store the access details some where, may be in registry or INI or something like that, so check for that or ask the maker of the software to send you the details about where the Server details are stored by the application. Then, you can open them up and find the details.
|||Yeah thats the thing, I don't want to loose the data. OK, so I will talk to them and see what they can help me with. Thanks.
|||Well don't know anything about sql, msde, all i know is that the program asks for the login credentials when its installing, other than that, I don't mess with MSDE.
sqlWednesday, March 21, 2012
MSDE 1.0 --> MSDE 2000 DB Connection Failure
Just recently updated to MSDE 2000 using the SP3 Desktop upgrade. Now when this software runs it cannot connect to the Database.
I believe the problem to come in a line wrote as so:
BSTR bstrOpen = gServerName.AllocSysString();
although I'm not 100%.
Just wondering if anyone might had the same problem with MSDE 2000 and what they did to fix it. Thanks!
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Hi,
One of the things that's different about MSDE2000 is that by default, tcp is
not enabled. You might need to re-enable it. You can do this by running
svrnetcn.exe.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:%234NbSXufEHA.2984@.tk2msftngp13.phx.gbl...
> Just recently updated to MSDE 2000 using the SP3 Desktop upgrade. Now
when this software runs it cannot connect to the Database.
> I believe the problem to come in a line wrote as so:
> BSTR bstrOpen = gServerName.AllocSysString();
> although I'm not 100%.
> Just wondering if anyone might had the same problem with MSDE 2000 and
what they did to fix it. Thanks!
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
I believe the problem to come in a line wrote as so:
BSTR bstrOpen = gServerName.AllocSysString();
although I'm not 100%.
Just wondering if anyone might had the same problem with MSDE 2000 and what they did to fix it. Thanks!
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
Hi,
One of the things that's different about MSDE2000 is that by default, tcp is
not enabled. You might need to re-enable it. You can do this by running
svrnetcn.exe.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:%234NbSXufEHA.2984@.tk2msftngp13.phx.gbl...
> Just recently updated to MSDE 2000 using the SP3 Desktop upgrade. Now
when this software runs it cannot connect to the Database.
> I believe the problem to come in a line wrote as so:
> BSTR bstrOpen = gServerName.AllocSysString();
> although I'm not 100%.
> Just wondering if anyone might had the same problem with MSDE 2000 and
what they did to fix it. Thanks!
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
Monday, March 12, 2012
MSDE - Unknown Server
Hello,
I installed software called AutoAPP on a users desktop and this software
automatically installs MSDE (No idea what version). When run under the
administrator account everything is fine. When the user logs on under their
account (power user) SQL Icon is on the task bar, but it is blank \\ -
Unknown Server. I have to manually type in the laptop name in the server
field of the SQL Server Service Manager and then the arrow will go green.
Does anyone know why under Administrator account the server name is there,
but not under the users profile? It is annoying having to type in the
computer each time the computer reboots, giving the user Administrative
access to their computer is not really an option. Once the computer name is
entered under the user account everything seems to function normally.
Laptop is running Windows XP Pro SP1
Thank You.
hi John,
"John J. Rambone" <lgm_rambone@.remove.hotmail.com> ha scritto nel
messaggio news:uANQsnFuEHA.1472@.TK2MSFTNGP10.phx.gbl
> Hello,
> I installed software called AutoAPP on a users desktop and this
> software automatically installs MSDE (No idea what version). When
> run under the administrator account everything is fine. When the
> user logs on under their account (power user) SQL Icon is on the task
> bar, but it is blank \\ - Unknown Server. I have to manually type in
> the laptop name in the server field of the SQL Server Service Manager
> and then the arrow will go green. Does anyone know why under
> Administrator account the server name is there, but not under the
> users profile? It is annoying having to type in the computer each
> time the computer reboots, giving the user Administrative access to
> their computer is not really an option. Once the computer name is
> entered under the user account everything seems to function normally.
> Laptop is running Windows XP Pro SP1
is the Service Manager only that does not enlist the local server, or is the
MSDE service itself that is not running when logging as a power user?
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
|||> is the Service Manager only that does not enlist the local server, or is
> the
> MSDE service itself that is not running when logging as a power user?
I uninstalled everything, but once I reinstall I will check under the
Services and Applications -> Services to make sure it is running. I'm
almost positive it is running and the Service manager does load on boot up,
but the circle will not have the green arrow. If I open the Service Manager
the drop down for the Server field will be empty. I type in the name of the
local comptuer i.e. laptop1 and it arrow goes green and the application can
access the database. It is just annoying to have to type in the computer
name each time. I will very 100% for sure if the service is running in the
next day or so, once I get a chance to work on the users laptop again.
Thanks You.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2u4493F26ob6nU1@.uni-berlin.de...
> hi John,
> "John J. Rambone" <lgm_rambone@.remove.hotmail.com> ha scritto nel
> messaggio news:uANQsnFuEHA.1472@.TK2MSFTNGP10.phx.gbl
>
> --
> 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
>
I installed software called AutoAPP on a users desktop and this software
automatically installs MSDE (No idea what version). When run under the
administrator account everything is fine. When the user logs on under their
account (power user) SQL Icon is on the task bar, but it is blank \\ -
Unknown Server. I have to manually type in the laptop name in the server
field of the SQL Server Service Manager and then the arrow will go green.
Does anyone know why under Administrator account the server name is there,
but not under the users profile? It is annoying having to type in the
computer each time the computer reboots, giving the user Administrative
access to their computer is not really an option. Once the computer name is
entered under the user account everything seems to function normally.
Laptop is running Windows XP Pro SP1
Thank You.
hi John,
"John J. Rambone" <lgm_rambone@.remove.hotmail.com> ha scritto nel
messaggio news:uANQsnFuEHA.1472@.TK2MSFTNGP10.phx.gbl
> Hello,
> I installed software called AutoAPP on a users desktop and this
> software automatically installs MSDE (No idea what version). When
> run under the administrator account everything is fine. When the
> user logs on under their account (power user) SQL Icon is on the task
> bar, but it is blank \\ - Unknown Server. I have to manually type in
> the laptop name in the server field of the SQL Server Service Manager
> and then the arrow will go green. Does anyone know why under
> Administrator account the server name is there, but not under the
> users profile? It is annoying having to type in the computer each
> time the computer reboots, giving the user Administrative access to
> their computer is not really an option. Once the computer name is
> entered under the user account everything seems to function normally.
> Laptop is running Windows XP Pro SP1
is the Service Manager only that does not enlist the local server, or is the
MSDE service itself that is not running when logging as a power user?
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
|||> is the Service Manager only that does not enlist the local server, or is
> the
> MSDE service itself that is not running when logging as a power user?
I uninstalled everything, but once I reinstall I will check under the
Services and Applications -> Services to make sure it is running. I'm
almost positive it is running and the Service manager does load on boot up,
but the circle will not have the green arrow. If I open the Service Manager
the drop down for the Server field will be empty. I type in the name of the
local comptuer i.e. laptop1 and it arrow goes green and the application can
access the database. It is just annoying to have to type in the computer
name each time. I will very 100% for sure if the service is running in the
next day or so, once I get a chance to work on the users laptop again.
Thanks You.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2u4493F26ob6nU1@.uni-berlin.de...
> hi John,
> "John J. Rambone" <lgm_rambone@.remove.hotmail.com> ha scritto nel
> messaggio news:uANQsnFuEHA.1472@.TK2MSFTNGP10.phx.gbl
>
> --
> 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
>
Friday, March 9, 2012
MSDE
Can some one tell me how to figure out which version MSDE I have loaded? It
is part of some non-Microsoft software, and MBSA suggests installing paths,
but I don't know what version of MSDE to select the patch for. Thank you fo
r
any help you can provide.http://www.aspfaq.com/show.asp?id=2160
Andrew J. Kelly SQL MVP
"Glen_in_Spokane" <Glen_in_Spokane@.discussions.microsoft.com> wrote in
message news:9C03AF5C-1FA3-4B90-AFCB-8CE2D7E1546D@.microsoft.com...
> Can some one tell me how to figure out which version MSDE I have loaded?
> It
> is part of some non-Microsoft software, and MBSA suggests installing
> paths,
> but I don't know what version of MSDE to select the patch for. Thank you
> for
> any help you can provide.
is part of some non-Microsoft software, and MBSA suggests installing paths,
but I don't know what version of MSDE to select the patch for. Thank you fo
r
any help you can provide.http://www.aspfaq.com/show.asp?id=2160
Andrew J. Kelly SQL MVP
"Glen_in_Spokane" <Glen_in_Spokane@.discussions.microsoft.com> wrote in
message news:9C03AF5C-1FA3-4B90-AFCB-8CE2D7E1546D@.microsoft.com...
> Can some one tell me how to figure out which version MSDE I have loaded?
> It
> is part of some non-Microsoft software, and MBSA suggests installing
> paths,
> but I don't know what version of MSDE to select the patch for. Thank you
> for
> any help you can provide.
msde
I recently joined a company where they have couple of MSDEs that were
installed as part of the software application package. Do they need to be
administered as well alongwith the other Standard and Enterprise SQL Servers
installations?
sharman,
The answer about how much administration depends on how these MSDE servers
are being used.
If they hold critical data, then yes they need to be administered along with
the other SQL Servers. If there are security issues related to access, these
need to be managed as well.
If the application simply uses these databases as a temporary workarea and
can easily rebuild the data in case of problems, then the management is
less. It would still be good to have database backups that could restore
the metadata.
You need to understand what is going on with the MSDEs and then you can make
a good decision.
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:1B413580-5393-405C-81CD-0CECD6D4DA83@.microsoft.com...
>I recently joined a company where they have couple of MSDEs that were
> installed as part of the software application package. Do they need to be
> administered as well alongwith the other Standard and Enterprise SQL
> Servers
> installations?
installed as part of the software application package. Do they need to be
administered as well alongwith the other Standard and Enterprise SQL Servers
installations?
sharman,
The answer about how much administration depends on how these MSDE servers
are being used.
If they hold critical data, then yes they need to be administered along with
the other SQL Servers. If there are security issues related to access, these
need to be managed as well.
If the application simply uses these databases as a temporary workarea and
can easily rebuild the data in case of problems, then the management is
less. It would still be good to have database backups that could restore
the metadata.
You need to understand what is going on with the MSDEs and then you can make
a good decision.
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:1B413580-5393-405C-81CD-0CECD6D4DA83@.microsoft.com...
>I recently joined a company where they have couple of MSDEs that were
> installed as part of the software application package. Do they need to be
> administered as well alongwith the other Standard and Enterprise SQL
> Servers
> installations?
Wednesday, March 7, 2012
MSDE
Can some one tell me how to figure out which version MSDE I have loaded? It
is part of some non-Microsoft software, and MBSA suggests installing paths,
but I don't know what version of MSDE to select the patch for. Thank you for
any help you can provide.
http://www.aspfaq.com/show.asp?id=2160
Andrew J. Kelly SQL MVP
"Glen_in_Spokane" <Glen_in_Spokane@.discussions.microsoft.com> wrote in
message news:9C03AF5C-1FA3-4B90-AFCB-8CE2D7E1546D@.microsoft.com...
> Can some one tell me how to figure out which version MSDE I have loaded?
> It
> is part of some non-Microsoft software, and MBSA suggests installing
> paths,
> but I don't know what version of MSDE to select the patch for. Thank you
> for
> any help you can provide.
is part of some non-Microsoft software, and MBSA suggests installing paths,
but I don't know what version of MSDE to select the patch for. Thank you for
any help you can provide.
http://www.aspfaq.com/show.asp?id=2160
Andrew J. Kelly SQL MVP
"Glen_in_Spokane" <Glen_in_Spokane@.discussions.microsoft.com> wrote in
message news:9C03AF5C-1FA3-4B90-AFCB-8CE2D7E1546D@.microsoft.com...
> Can some one tell me how to figure out which version MSDE I have loaded?
> It
> is part of some non-Microsoft software, and MBSA suggests installing
> paths,
> but I don't know what version of MSDE to select the patch for. Thank you
> for
> any help you can provide.
MSDE
Can some one tell me how to figure out which version MSDE I have loaded? It
is part of some non-Microsoft software, and MBSA suggests installing paths,
but I don't know what version of MSDE to select the patch for. Thank you for
any help you can provide.http://www.aspfaq.com/show.asp?id=2160
Andrew J. Kelly SQL MVP
"Glen_in_Spokane" <Glen_in_Spokane@.discussions.microsoft.com> wrote in
message news:9C03AF5C-1FA3-4B90-AFCB-8CE2D7E1546D@.microsoft.com...
> Can some one tell me how to figure out which version MSDE I have loaded?
> It
> is part of some non-Microsoft software, and MBSA suggests installing
> paths,
> but I don't know what version of MSDE to select the patch for. Thank you
> for
> any help you can provide.
is part of some non-Microsoft software, and MBSA suggests installing paths,
but I don't know what version of MSDE to select the patch for. Thank you for
any help you can provide.http://www.aspfaq.com/show.asp?id=2160
Andrew J. Kelly SQL MVP
"Glen_in_Spokane" <Glen_in_Spokane@.discussions.microsoft.com> wrote in
message news:9C03AF5C-1FA3-4B90-AFCB-8CE2D7E1546D@.microsoft.com...
> Can some one tell me how to figure out which version MSDE I have loaded?
> It
> is part of some non-Microsoft software, and MBSA suggests installing
> paths,
> but I don't know what version of MSDE to select the patch for. Thank you
> for
> any help you can provide.
msde
I recently joined a company where they have couple of MSDEs that were
installed as part of the software application package. Do they need to be
administered as well alongwith the other Standard and Enterprise SQL Servers
installations?sharman,
The answer about how much administration depends on how these MSDE servers
are being used.
If they hold critical data, then yes they need to be administered along with
the other SQL Servers. If there are security issues related to access, these
need to be managed as well.
If the application simply uses these databases as a temporary workarea and
can easily rebuild the data in case of problems, then the management is
less. It would still be good to have database backups that could restore
the metadata.
You need to understand what is going on with the MSDEs and then you can make
a good decision.
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:1B413580-5393-405C-81CD-0CECD6D4DA83@.microsoft.com...
>I recently joined a company where they have couple of MSDEs that were
> installed as part of the software application package. Do they need to be
> administered as well alongwith the other Standard and Enterprise SQL
> Servers
> installations?
installed as part of the software application package. Do they need to be
administered as well alongwith the other Standard and Enterprise SQL Servers
installations?sharman,
The answer about how much administration depends on how these MSDE servers
are being used.
If they hold critical data, then yes they need to be administered along with
the other SQL Servers. If there are security issues related to access, these
need to be managed as well.
If the application simply uses these databases as a temporary workarea and
can easily rebuild the data in case of problems, then the management is
less. It would still be good to have database backups that could restore
the metadata.
You need to understand what is going on with the MSDEs and then you can make
a good decision.
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:1B413580-5393-405C-81CD-0CECD6D4DA83@.microsoft.com...
>I recently joined a company where they have couple of MSDEs that were
> installed as part of the software application package. Do they need to be
> administered as well alongwith the other Standard and Enterprise SQL
> Servers
> installations?
Saturday, February 25, 2012
msdb renamed to msbd
Hello,
Yesterday i was trying to install a backup client for sql on our sql server,
it kept on failing so i contacted the software vendor to see if there was a
problem with the client. after they poked around on our sql server they rea
lized that one of the datab
ases had been renamed, for what reason i dont know. The msdb database was re
named to msbd. This is the reason that we can not install the backup agent s
oftware. Does anyone out there know how to rename the database, the physical
name of the database file
is fine its the display name inside of Enterprise manager.
ThanksHi,
Refer sp_renamedb in books online
sp_renamedb [ @.dbname = ] 'old_name' ,
[ @.newname = ] 'new_name'
Thanks
Hari
MCDBA
"Brian Butler" <anonymous@.discussions.microsoft.com> wrote in message
news:564BE6BC-5201-4828-A0B3-9E1450653B3A@.microsoft.com...
> Hello,
> Yesterday i was trying to install a backup client for sql on our sql
server, it kept on failing so i contacted the software vendor to see if
there was a problem with the client. after they poked around on our sql
server they realized that one of the databases had been renamed, for what
reason i dont know. The msdb database was renamed to msbd. This is the
reason that we can not install the backup agent software. Does anyone out
there know how to rename the database, the physical name of the database
file is fine its the display name inside of Enterprise manager.
> Thanks|||In SQL 2000, an alternative to sp_renamedb is ALTER DATABASE:
ALTER DATABASE msbd
MODIFY NAME = msdb
Hope this helps.
Dan Guzman
SQL Server MVP
"Brian Butler" <anonymous@.discussions.microsoft.com> wrote in message
news:564BE6BC-5201-4828-A0B3-9E1450653B3A@.microsoft.com...
> Hello,
> Yesterday i was trying to install a backup client for sql on our sql
server, it kept on failing so i contacted the software vendor to see if
there was a problem with the client. after they poked around on our sql
server they realized that one of the databases had been renamed, for what
reason i dont know. The msdb database was renamed to msbd. This is the
reason that we can not install the backup agent software. Does anyone out
there know how to rename the database, the physical name of the database
file is fine its the display name inside of Enterprise manager.
> Thanks
Yesterday i was trying to install a backup client for sql on our sql server,
it kept on failing so i contacted the software vendor to see if there was a
problem with the client. after they poked around on our sql server they rea
lized that one of the datab
ases had been renamed, for what reason i dont know. The msdb database was re
named to msbd. This is the reason that we can not install the backup agent s
oftware. Does anyone out there know how to rename the database, the physical
name of the database file
is fine its the display name inside of Enterprise manager.
ThanksHi,
Refer sp_renamedb in books online
sp_renamedb [ @.dbname = ] 'old_name' ,
[ @.newname = ] 'new_name'
Thanks
Hari
MCDBA
"Brian Butler" <anonymous@.discussions.microsoft.com> wrote in message
news:564BE6BC-5201-4828-A0B3-9E1450653B3A@.microsoft.com...
> Hello,
> Yesterday i was trying to install a backup client for sql on our sql
server, it kept on failing so i contacted the software vendor to see if
there was a problem with the client. after they poked around on our sql
server they realized that one of the databases had been renamed, for what
reason i dont know. The msdb database was renamed to msbd. This is the
reason that we can not install the backup agent software. Does anyone out
there know how to rename the database, the physical name of the database
file is fine its the display name inside of Enterprise manager.
> Thanks|||In SQL 2000, an alternative to sp_renamedb is ALTER DATABASE:
ALTER DATABASE msbd
MODIFY NAME = msdb
Hope this helps.
Dan Guzman
SQL Server MVP
"Brian Butler" <anonymous@.discussions.microsoft.com> wrote in message
news:564BE6BC-5201-4828-A0B3-9E1450653B3A@.microsoft.com...
> Hello,
> Yesterday i was trying to install a backup client for sql on our sql
server, it kept on failing so i contacted the software vendor to see if
there was a problem with the client. after they poked around on our sql
server they realized that one of the databases had been renamed, for what
reason i dont know. The msdb database was renamed to msbd. This is the
reason that we can not install the backup agent software. Does anyone out
there know how to rename the database, the physical name of the database
file is fine its the display name inside of Enterprise manager.
> Thanks
Subscribe to:
Posts (Atom)