MSDE instance setup question

I needed to distribute the MSDE components to the computers that use my
software so I decided to build a setup program using InstallShield that
included the MSDE files.
After I ran the installation, I noticed that the setup created a folder on
my computer using the MSDE instance name I told the setup program to used
prefixed by a "$" character. So the folder created for an instance named
such as MACHOGRANDE was "C:\Program Files\Microsoft SQL
Server\MSSQL$MACHOGRANDE"
After noticing that, I went on to explore this folder and notice that it had
a bunch of files in it, I was surprised to see that one of the files was
named sqlservr.exe! It almost looked like the installation of my MSDE
instance was like a totally independent sql server installation! Like if it
had nothing to do with the other MSDE instance I had running. I doubt this
is the case since I am pretty sure there must be a gazzilion other files
installed on the computer that are sheared by all the database that use the
MSDE engine.
So my question is,
1. Why did the instance of MSDE crated all of this extra files (such as
sqlservr.exe)? Instead of simply created the ldf and mdf files like a
regular SQL server database? Aren't the MSDE and SQL server supposed to be
the same thing?
2. Also is there a special reason for the "$" character"?
Thanks
Hi Rene,
Welcome to use MSDN Managed Newsgroup!
[vbcol=seagreen]
be[vbcol=seagreen]
The SQL Server 2000 Desktop Engine (MSDE 2000) is a redistributable version
of the SQL Server relational database engine. MSDE 2000 is designed to be
distributed as a part of applications that require a local data store.
Software developers can code the setup of their application to install an
instance of MSDE 2000 and build a database to be used by the application.
The application is then coded to perform any needed administration of that
database and instance of MSDE 2000, and to use the data in the database to
store application data.
The main component in MSDE 2000, the database engine, provides for the
storage of data. MSDE 2000 includes a version of the SQL Server 2000
database engine tailored to run on a notebook or desktop client computer,
operating as the local data store for an application supporting one user or
a small workgroup of users. The database engine included in MSDE 2000
includes most of the functionality of the database engine included in the
other editions of SQL Server 2000. But it does not include some features
used in large production databases, such as parallel queries and indexed
views. For more information about the database engine features supported by
MSDE 2000
For more information, you are encouraged to check following topic in the
Books Online / MSDN Online
Understanding SQL Server 2000 Desktop Engine (MSDE 2000)
http://msdn.microsoft.com/library/de...us/architec/8_
ar_ts_67ax.asp
What are the limitations of MSDE?
http://www.aspfaq.com/show.asp?id=2343
[vbcol=seagreen]
For all named instances, it will be identified as MSSQL$<instance name>.
SQL Server 2000 supports multiple instances of the SQL Server database
engine running concurrently on the same computer.
All instances of the database engine other than the default instance are
identified by an instance name specified during installation of the
instance. Applications must provide both the computer name and the instance
name of any named instance to which they are attempting to connect. The
computer name and instance name are specified in the format
computer_name\instance_name.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.