Complete newbie

[Guest_imported]

I've only used MS Access for database work but have recently begun to understand why people say "upgrade to an SQL database" cause one of my databases which has grown to 40MB is running very slo

http://www.<br><br>How

do you create an SQL database? Can I run one on my windows 98 machine for testing purposes? What do I need to edit one (I have Visual Studio 6 Enterprise is that any good?). Any advice appreciated...

 

[crystalized]

I have been using the visual interdev tool to create my tables, stored procedures and database diagrams(must be the enterprise edition to have this capability).&nbsp;&nbsp;The interface on it is nice and very easy to use.&nbsp;&nbsp;In many ways it is similar to the Access interface you are used to, at least I find it similar enough that I have not had a huge problem with the change over.<br><br>I imagine, although I am not sure, that the other tools in the visual studio enterprise edition have similar capabilities.&nbsp;&nbsp;Again I am not sure, but visual basic probably has it.&nbsp;&nbsp;<br><br>I am very new to SQL Server as well, you will find that the differences are significant between it and Access.&nbsp;&nbsp;My focus thus far has not been on anything in the database except making tables and relationships (now I have started with stored procedures).&nbsp;&nbsp;But there are more considerations with SQL Server ie Users, Roles and the list goes on.&nbsp;&nbsp;But it is generally easy to use from the bit that I have had to do so far.&nbsp;&nbsp;&nbsp;Since you are familiar with Access you will find some things very easy and other things frustrating (no cascade update or delete in 7.0, although 2000 is supposed to have it)<br><br>I am not sure of whether you can run it on 98 or not, I am running it on Win 2000 server and it seems to work well and the install was really very simple.<br><br>Good luck, I hope you like it. <p>Crystal<br><a href=mailto:crystals@genesis.sk.ca>crystals@genesis.sk.ca</a><br><a href= > </a><br>--------------------------------------------------<br>
Experience is one thing you can't get for nothing.<br>
-Oscar Wilde<br>

 

[christine1]

Access is an Office product (front end) and SQL is a Back end product.&nbsp;&nbsp;<br><br>You must first install SQL server and I am assuming that you are in a networked environment running NT.&nbsp;&nbsp;If so you install server (software) to the NT box and the client (software) to your desktop (98 is fine).&nbsp;&nbsp;<br><br>From what you have described, it appears that they may somewhat of a learning curve as you will need a bit of SQL -Structured Query Language understanding.&nbsp;&nbsp;The good thing is you can continue to use Access to query your database or input data (again from the front end) and have the actual data reside in the SQL dB (which is capable of handling large dB's)Ask your boss to send you to a SQL class however, as you will need to now how to administer it on your server.<br><br>I hope this helps.<br><br>Christine

 

[Waynest]

You CAN install sql locally for design purposes, but put it on an NT box and start as you mean to go on.<br><br>You create databases using enterprise manager which is a tool which comes with sql server.&nbsp;&nbsp;You create the tables here too, although you can use tools such as access 2000 (try it, its great with sql server).

 

[Guest_imported]

Thanks to all for the suggestions and comments.

As to Christine's comment, actually I use Access for back end web site work (I do mostly asp and java/jdbc) so the SQL language stuff is no problem - intensive experience there.

Administering the server would definitely be an issue. However, I would probably not be administering the server myself most of the time because we usually set up clients on some hosting service or other depending on the size and complexity of the site and they usually have that already set up, deal with mappings etc.

Thanks again. Any other comments, notes etc welcome!