Re: Relocate MSDE 2000 database?

That's going to be the never-ending problem with MSDE. Most of the 2000 versions of SQL Server and thus MSDE have been pulled. Tool were always a problem for MSDE which is why I recommended installing the Developer Edition tools. It can be purchased for about $40 (about 2 Euros) and can manage any version of SQL Server.

Again, this is a point you can bring up with your customer. It will be increasingly expensive to support no-supported databases as time goes on.

--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
____________________________________________________________________________________________
"Sue Morton" <867-5309@xxxxxxxxxxxxxx> wrote in message news:EkDTj.2325$J16.1788@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Andrea,

I've already hammered on the vendors for not offering database placement as part of the installation, and to use a more current database engine. But then, I'm using XP Pro which is 10 years old (OK it wasn't yet a release in 1998, but still) so an 8 year old database solution doesn't seem that far-fetched :-D

Back to William Vaughn's first post, a suggestion to use SQL Server Management Studio, can you point me to one that will work with MSDE 2000 (or MSDE 2005)? I looked through those available at MS Download Center and I'm unclear which one would work?

I do have the OSQL (or SQLCMD in the case of 2005) scripts written now so it is not a huge deal, but it would be nice to use a management tool if one is available.

Thanks and regards,
--
Sue Morton

Andrea Montanari wrote:
hi Sue,
Sue Morton wrote:
I hear you but I don't know that I should do this? Recall my 1st
post -- these databases are installed and deployed by 3rd party apps
that I purchased, I am not the developer.
Do you really think it is wise to upgrade these databases independent
of the vendor's support? If I were to upgrade the SQL server behind
these apps, I'm concerned I would not be able to reinstall the
original and/or update the software as provided by the vendor. By
moving their databases after the fact, at least I know I can back
them up and even restore them to the original location, and even if I
have to reinstall the vendor's app from scratch (e.g. disk failure,
new computer etc.) I can still run the app.

ok, the reasons you are stuck with MSDE are clear and loud.. and, as
long as that data and relative application are critical to you as it
seems, you can only try to "force" via your "customer's economical
power" the ISV to support SQLExpress edition as well..
it's absolutely not wise to just "upgrade yourself" as you would for
sure lose support for it, and you probably pay for it.. but these are
not technical concerns but "legal ones" only...
there are "things" that could be broken in the migration from SQL
Server 2000 code base to SQL Server 2005, and you, of course, have to
be granted they will not..
if you have spare time and want to, you could set up a test
environment with SQLExpress and give it a try, but of course this is
not a certified test, just a "poor's man try"...
best luck



.

Relevant Pages

  • RE: How to configure WSS to use SQL server instead of MSDE
    ... This is why, in this post, I wanted to focus on only WSS features. ... Apparently WSS DOES NOT SUPPORT SQL Server since it has no tool (that we ... >>MSDE databases for its configuration and content ...
    (microsoft.public.sharepoint.windowsservices)
  • Cannot insert explicit value for identity...
    ... I am developing an integration process between two databases. ... The main database is the SQL Server, the MSDE will contain a really ...
    (comp.databases.ms-sqlserver)
  • Re: Newbie Questions
    ... I have noticed that some of the documentation talkes about SQL Server ... > MSDE is the old database engine there is now as well SQL server Express, ... > hard to find (mostly everything is done with scripting ASP style). ... How do I use the MSDE functionality in relation to databases? ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Change default to named instance??
    ... Take a backup of all databases ... Stop SQL Server and copy the MDF and LDF to a safe place ... Un Install the MSDE ... > conflicts with other app's msdes, I now want to use a named instance. ...
    (microsoft.public.sqlserver.msde)
  • RE: MSDE, Access, SharePoint... I am not sure where to ask this qu
    ... 1.>> What is the difference between MSDE and WMSDE? ... MSDE that is targeted for use by Windows components only. ... isn't SQL Server Express replacing MSDE and WMSDE? ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
Loading