msde installation

[antvon]

Hi all

I hope this is the correct forum (apologies if not)

I need to now how to use msde after i installed it.
I only know a few basics..create,modify,delete etc
from working on sql server 2k databases.

I have a installed sqlsvr2k on my machine and have
installed the msde as well.(which I read somewhere you
could do).But I cannot see the msde databases or reference
them anywhere.

Ok you might be asking why I would need both on my local
machine.The answer is that I bought vb.net STANDARD edition.
which i discovered does not let you use links to the sql db
unless you have msde installed.

Yes I didnt read the fine print.

as per the instructions i run setup from the downloaded directory with the parameters (setup INSTANCENAME="MSDE" SAPWD="sa") and voila a had an extra directory with $MSDE$ behind it.
When I try to link and odbc dsn to it the is no name to choose from.

Any Ideas

 

[JBaileys]

MSDE and SQL Server are the same db engine. MSDE is free and you have some limitations. To install MSDE over sql server is not going to change your environment. MSDE is the "personal edition" and has no interface. It is strictly the db engine - which you already have with SQL Server.

 

[antvon]

Hi JBaileys

Thanks for the fast reply.

This is gonna sound dumb but I really don't know.
How do you use the 'personal edition' ie
if I wanted to create a database and connect through
odbc to the tables.

would i use the command line arguments or scripting
perhapes.(Sorry i know i should read more of the specs
but they give me such a headache)

I do realise that the free edition does have limitations
its just that i have to use msde with the vb.net standard
and i need to make changes to sql databases as well

Once the vb app has been completed using msde I should be
able to migrate it to the client pc that uses the sql server

Shouldn't the msde be a seperate instance in its own right with a server name i could connect to ?

Thanks

 

[JBaileys]

Antvon,

Connecting to MSDE via odbc is exactly the same as connecting to SQL Server. Provide a user / pwd with a server name and you are ready to go. (or of course windows authentication).

As far as creating the database, you have a few options. One of the easier options is to install the developer edition of sql server on a client machine and use Enterprise manager to create the dbs.

The MSDE is a seperate instance of its own (if you install it that way). Just use the instance parameter.

MSDE is the same thing as SQL Server with no graphic interface and some db engine limitations.

Hope I am answering your question.

JB

 

[cswanic]

I know what you are asking since I had the same problem trying to see the instances of MSDE databases and other instances created on my server. I am running SBS 2003, VB.NET, etc.
You may need to first upgrade your instance of MSDE to SQL Server. That was the last step I did before I got to see the DB tables.

To access the tables, Open SQL Enterprise Manager
Right click SQL Server Group
Click New SQL Server Registration
Click Next
\\servername\instance name then click add
\\servername\NETSDK
\\servername\SHAREPOINT
Click Next
Windows Authentication then click Next
Add SQL Servers to Existing SQL Server Group then click Next
Click Finish
Success!
Then Click Close

Hope this helps.

 

[antvon]

Hi

Apologies to JBailey for not replying sooner.Unfortunately
had a hectic work schedule.I did try and mess around with it in the little time i managed to sneak in now and then
but not with much success.

Thanks cswanic, I am itching to try your suggestion
but will properbly only get to it on Monday.Well let
you know.

Do any of you know of dedicated forums for msde.Yes
even though it is sql server. Or even ones for vb.net
standard edition even though it is vb.net I guess
what i'm trying to say is there specific forums dealing
with the specific limitations and workarounds pertaining
to these editions.

 

[spelhank]

I am also interested in MSDE. I use an application that uses MSDE as its SQL database. Now with 2003 server, I am told that MSDE will no longer be installed -- instead I must purchase SQL at a much larger expense. Question, isn't there a substitute for MSDE? If not, can I still use MSDE with the 2003 server and install it separately even though it does not install automatically with the application?

 

[antvon]

Hi there

Well, I certainly did'nt expect to see a thread on this
question again, but its welcome non the less.

Unfortunately my knowledge has not expanded since but I
was able to use the MSDE engine with a bit of cheating.

To answer your question

Firstly I take it that you are upgrading to 2003 Server.
I see no reason why it should not be installed on 2003 Server (unless the specifications forbid it - but I don't know)

As for a substitute for MSDE you may want to take a look at
SQL Server 2005 Express Beta.
I have downloaded it and installed but can't get the hang of it yet. I am only able to use it via the Visual Basic 2005 Express application.
Currently I am running all of them to one degree or the other so I can't say if they are just conflicting with one another.

PS. Have you posted this question as a new link as well?