Installing SQL Server ?

**Pirate** · Mar 15th, 2003, 02:25 AM

How can I install SQL Server 2000 ??

**SimonVega** · Mar 15th, 2003, 02:44 AM

Umm....you have the disk??

**Pirate** · Mar 15th, 2003, 02:53 AM

Originally posted by SimonVega
Umm....you have the disk??

I don't know from where to start ! Do you mean the five CDs ?? Yes

**Edneeis** · Mar 15th, 2003, 03:07 AM

If you mean the 5 CDs for VS.NET then (if VS is already installed) then go to the control panel->click on change for the Visual Studio.NET item. This will run the setup again but now you can just select the MSDE option in the setup and finish. Afterwards you have run the Setup file in the MSDE folder in the VS root folder in Program Files.

**Pirate** · Mar 15th, 2003, 03:22 AM

I didn't find MSDE but instead SQL Server . I've installed it's not in start menu ???
Where the hell it disappeared ??

**Edneeis** · Mar 15th, 2003, 03:32 AM

I'm not sure it will put anything in the Start Menu, since its MSDE you have to use Access to work with it. Fire up access and create a new project, when prompted try to have it figure out what the server is or try localhost or localhost/vsdotnet and then pick a db.

You can also work with it from inside VS.NET using the Server Explorer.

**Pirate** · Mar 15th, 2003, 03:42 AM

XP Access suddenly disappeared . Is that because installing MSDE ?Is this possible ?

**Pirate** · Mar 15th, 2003, 03:49 AM

I installed it again . Sorry for acting as newbie Edneeis !

I will try to play with it for a while and tell later...
Thanx a lot for bearing up with me .

**Pirate** · Mar 16th, 2003, 04:49 PM

I've installed SQL Server 2000
Edneeis , Can you please answer my simple questions ?

1-Where should I click to build my SQL Server 2000 Database ? I'm really confused at this area !

. I just need a huge db that accepts concurrent connections (mutliple users use the same db)

2-I've heard of back end and front end database or app (I can't remember exactly which one is true) .What the heck are these ??

3-What I want to have at the end of the day is : either let my application to be on a network and a lot of users will do some database transactions (inserting , deleting , quering ) OR use it locally (distribute it as usual app ) . This step will push me to start my proj !

Thanks in advance !

**Pirate** · Mar 16th, 2003, 05:17 PM

What I mean by Network is LAN not as web application !

**Edneeis** · Mar 16th, 2003, 06:49 PM

Ok since it is installed now then go to VS.NET and open the Server Explorer panel on the left. Then browse to your computer (which should already be there) then expand it and browse to SQL Servers. When you expand SQL Servers it should automatically discover the local SQL Server you have running and then open up and show you the databases. At this point there will probably only be the default ones that come with installation. From there you should be able to right click your SQL Server and create a new DB. After its created you should be able to make the tables and what not right from there otherwise you can also use Access. If you use Access then you'll make a new 'project' and set the connection string to the SQL Server locally and the DB you want. Then from there it will connect and look a lot like making an Access DB.

**Edneeis** · Mar 16th, 2003, 06:55 PM

1-Where should I click to build my SQL Server 2000 Database ? I'm really confused at this area ! . I just need a huge db that accepts concurrent connections (mutliple users use the same db)

See previous post.

2-I've heard of back end and front end database or app (I can't remember exactly which one is true) .What the heck are these ??

This relates to Multi-Tier applications, which is just a big word for seperating your app into parts. So here you will have a VB.NET front end (the end the user actually sees) and a SQL Server back end (the thing that does all the work).

3-What I want to have at the end of the day is : either let my application to be on a network and a lot of users will do some database transactions (inserting , deleting , quering ) OR use it locally (distribute it as usual app ) . This step will push me to start my proj !

SQL will be hard to distribute for a single user and would be overkill. It is intended for larger projects or networked ones, although it could still be used either way. I would use OLEDB connections then that way you can switch from SQL to Access whenever you want. This will hinder the use of Stored Procedures, which is one of the best things of SQL, but that is my suggestion if you HAVE to provide for a single user situation and a multi-user one.

**Pirate** · Mar 17th, 2003, 01:59 PM

I've already started a new proj . I'm still reading about processing of data flow and more

. It's wide area but interesting (with server and clients)!

a million thanks Edneeis . You are always of great help !

Take Care

Thread: Installing SQL Server ?

Thread Tools

Display

Installing SQL Server ?

Posting Permissions