Need to migrate to sql server2000, where do I start?

[nimarii]

Hello -

I work for a very small company, and we are starting to out-grow the access databases we have been using. These access databases have a very good amount of vba coding behind them.

We want to migrate to sql server2000, but I'm unsure of what version to get (will standard edition be enough for 10 users?) and also if we need to get a separate server to house it on.

Also, will I need to develop a front end for the sql server, or does it provide some kind of interface that I can customize, much like Access?

I've also heard that vba isn't supported on sql server; will I have to re-write all of the vba coding?

I'm so confused, and haven't been very successful in my research on the internet. Can anyone provide any help/advice, or suggest some resources I can check out?

Many many thanks,
nimarii

 

[nigelrivett]

You should get a separate server for sql server - it will make things easier.

You can move all the tables into sql server and access them from access via linked tables. You will probably have to do a bit of recoding but it's a start.

Sql server doesn't give you a front end apart from a few clients like enterprise manager, dts, query analyser. You will have to write application to interface. You can do this in access but VB or ASP would be a better choice.

You might want t take the opertunity to redesign the database and move all acceess into stored procs.

======================================
Cursors are useful if you don't know sql.
DTS can be used in a similar way.
Beer is not cold and it isn't fizzy.

 

[nimarii]

thanks for the reply!

I've had some problems using Access databases on a shared network with up to 5 users. Will these same problems exist if i use Access as a front-end? The problems were usually involving simultaneous record-locking, and related issues.

do you know where I can find more information about converting vba code to stored procedures?

Also, if I'm goign to create a front-end in vb or asp, I would need the sql server database set up already, right? at least, just the structure of it anyway?

argh, sorry for so many questions!