Results 1 to 3 of 3
  1. #1
    4 Star Lounger
    Join Date
    Feb 2001
    Location
    Gillingham, Kent, England
    Posts
    511
    Thanks
    0
    Thanked 0 Times in 0 Posts

    MSDE (free SQL) advice (MSDE 2000 Release A)

    I wasn't sure where to ask this question, but seeing as so many people link to SQL from VB, I thought i'd start here......

    Does anyone have experience installing MSDE 2000? Its a bit different from the regular method of software installation and im more than a bit confused!

    For a start, does anyone know the difference beteen Release A and SP3a (i.e. which is newest).
    Also, what is the "usual" method of its use? i.e. just to add a new database, or to create a whole new isntance?

    For anyone who hasn't seen it, think of SQL server 7 without any of the GUI (enterprise manager etc), and now think of installing it upto 16 times on the same machine instead of creating a new database - there is a point to it as there are certain limitations on MSDE, but i'm after some guidelines as Im new to it!

    Any tips etc would be much appreciated. If there is a better home for this post, im sure a friendly moderator will put it where it should be <img src=/S/crossfingers.gif border=0 alt=crossfingers width=17 height=16>

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: MSDE (free SQL) advice (MSDE 2000 Release A)

    Why would you keep installing it, Phil? It doesn't have the UI tools that SQL Server has, but it isn't limited to a single SQL Server database. You only install it once on a machine. It is the client for SQL Server on that machine.
    Charlotte

  3. #3
    4 Star Lounger
    Join Date
    Feb 2001
    Location
    Gillingham, Kent, England
    Posts
    511
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: MSDE (free SQL) advice (MSDE 2000 Release A)

    Thats where my confusion is. There must be a reason why Microsoft produced a product that can be installed 16 times on one machine. I thought I was missing the point or something.

    From what I can gather, an example would be for CompanyA to install an Instance of MSDE called CompanyAProduct and another company to install another instance so the server can be called something else.

    Just in case anyone hasn't tried it, the server gets called "ComputerNameInstanceName" so therefore if (just for example) MSDE was installed for each part of Office, there would be servers as below all on the one PC.
    PhilsPCWord
    PhilsPCAccess
    PhilsPCExcel

    It just struck me as a very bizarre way of doing things!

    Just in case someone happens to have done this before....
    Im currently trying to get a DevStudio 9 Installshield MSI to install MSDE. Which isn't a problem until you need to take into account that MS doesnt support the objects any more, so if you do it manually you need to cater for all of the operating systems and if the user has any other versions of MSDE installed, and who knows what else I've missed! Seeing as im a complete installshield beginner, im very out of my depth!

    Hopefully it'll all come together in the end.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •