Please help me...

Any input is good input =)



I'm have Microsoft Access 2000, SQL Server 2000 (trial version) and 

running everything on Windows 2000 Professional.



I have completed a fully functional ASP website using Access 2000 as the 

database program.  I now need to switch over to SQL Server...where do i 

begin?



for starters...do I export the database from Access into SQL or import 

Access file from SQL?  I've read Access 2000 and SQL 2000 has some 

conflicts, do I need to download a service pack from microsoft.com/sql

...if yes which of the 3 parts of service pack 1 do i need?



Which "type" of database should i set up...server/client or front end/ 

back end?  I read that with the front end/back end option, I can reuse my 

FORMS in Access and link the tables to SQL.  How the heck do I do this? 

HOW THE HECK DO I ACTUALLY IMPORT SOMETHING?



SQL seems intimidating...nothing like Access.  I'm lost of where to 

start.  Tried importing tables in SQl but SOOO many options to choose 

from...confusing...SQL said successfully completed conversion but I have 

no idea where the file is on my computer???



If you have any guidance to any parts of the above, please tell me =P



Thank You in advance

Kien

My two cents:



Use the DTS tool included with SQL Server to migrate your databases to SQL

Server from Access.  It is found in the enterprise manager and will move you

through a wizard setup.  It is really simple to use.  You will need to make

your ADO type connections to SQL Server instead MS Access in your ASP code.

The Database conversion is seamless though.  Hope this helps.



TGW



-----Original Message-----

From: Kien Vinh Duong [mailto:kienvinh.duong@u...]

Sent: Tuesday, July 24, 2001 4:52 PM

To: ASP Database Setup

Subject: [asp_database_setup] HELP: convert Access Database -> SQL

Database





Please help me...

Any input is good input =)



I'm have Microsoft Access 2000, SQL Server 2000 (trial version) and

running everything on Windows 2000 Professional.



I have completed a fully functional ASP website using Access 2000 as the

database program.  I now need to switch over to SQL Server...where do i

begin?



for starters...do I export the database from Access into SQL or import

Access file from SQL?  I've read Access 2000 and SQL 2000 has some

conflicts, do I need to download a service pack from microsoft.com/sql

...if yes which of the 3 parts of service pack 1 do i need?



Which "type" of database should i set up...server/client or front end/

back end?  I read that with the front end/back end option, I can reuse my

FORMS in Access and link the tables to SQL.  How the heck do I do this?

HOW THE HECK DO I ACTUALLY IMPORT SOMETHING?



SQL seems intimidating...nothing like Access.  I'm lost of where to

start.  Tried importing tables in SQl but SOOO many options to choose

from...confusing...SQL said successfully completed conversion but I have

no idea where the file is on my computer???



If you have any guidance to any parts of the above, please tell me =P



Thank You in advance

Kien

Why don't you consider mySQL instead. It's a much simpler piece of 

software, and in read-only situations it can actually run a fair bit 

faster than a full-out DBM like SQL Server. I suggest this, since in terms

of functionality, I dare say that what Access is doing for you is fine -

you're only upgrading for scalability reasons. SQL Server licences are not

cheap, if this is your only reason.



MySQL is a controversial piece of software, and because of it's lack of

support for things like stored procedures, triggers and (most importantly)

transaction management and rollback, it has even been accused of being no

more than a file management system with an SQL interface. However, if you

are not planning on using transactions, triggers or stored procedures, 

mySQL may well be enough. Because of its simplicity, in fact, it can be 

dazzlingly fast. While I would hesitate to run an e-commerce site off it

yet, because of it's lack of transactions (although some PHP sites do), I 

would certainly consider it as a first replacement for Access. ODBC 

drivers exist for it, just like any other database manager and the 

essentials of connecting to it and running queries against it are just 

like using any other SQL database in ASP. It lacks Access's GUI, but if 

your database structure is fairly straightforward this wil not be too 

much of a problem - remember that once your table structure is in place, 

you will be able to link an access database to them and actually perform 

the data entry via that, using an interface you already know.



If it's any encouragement, the whole of the P2P website's frontend runs

off a mySQL database. For read-only or read-and-append type work, I would 

seriously consider mySQL, rather than paying out for SQL Server. If you 

start to find yourself modifying records in multiple tables simultaneously

then it obviously won't do, and you'll need SQL Server or Oracle (or, of

course, Postgre SQL if you still want to avoid the software licenses - 

although it has a reputation for being slow).



Just a thought.

Daniel Walker

Wrox Press



> Please help me...

> Any input is good input =)

> 

> I'm have Microsoft Access 2000, SQL Server 2000 (trial version) and 

> running everything on Windows 2000 Professional.

> 

> I have completed a fully functional ASP website using Access 2000 as 

the 

> database program.  I now need to switch over to SQL Server...where do i 

> begin?

> 

> for starters...do I export the database from Access into SQL or import 

> Access file from SQL?  I've read Access 2000 and SQL 2000 has some 

> conflicts, do I need to download a service pack from microsoft.com/sql

> ...if yes which of the 3 parts of service pack 1 do i need?

> 

> Which "type" of database should i set up...server/client or front end/ 

> back end?  I read that with the front end/back end option, I can reuse 

my 

> FORMS in Access and link the tables to SQL.  How the heck do I do this? 

> HOW THE HECK DO I ACTUALLY IMPORT SOMETHING?

> 

> SQL seems intimidating...nothing like Access.  I'm lost of where to 

> start.  Tried importing tables in SQl but SOOO many options to choose 

> from...confusing...SQL said successfully completed conversion but I 

have 

> no idea where the file is on my computer???

> 

> If you have any guidance to any parts of the above, please tell me =P

> 

> Thank You in advance

> Kien

> 

Thanks Daniel



My entire ASP website is read only except for one aspect...changing user 

password which only involves manipulation of one table. 



Licensing SQL Server is not an issue since the place i work for will eventually 

get it sooner or later if not for this project.



I'm just getting started with SQL server so I have no idea what transactions, 

triggers or stored procedures are.

My webpage is almost like a library catalogue...search for article by author or 

key word search and download corresponding pdf files.  From this description, 

do you think I need the the options you mentioned before?



What is "Access's GUI", my table structure is fairly simple.



Lastly, what is the maximum concurrent user mySQL can support?...this is the 

main reason why I'm switching out of Access to begin with.

If mySQL support what I'm trying to do...then definitely i'll give it a shot.



Thanks

Kien







Quoting Daniel Walker <danielw@w...>:



> Why don't you consider mySQL instead. It's a much simpler piece of 

> software, and in read-only situations it can actually run a fair bit 

> faster than a full-out DBM like SQL Server. I suggest this, since in

> terms

> of functionality, I dare say that what Access is doing for you is fine

> -

> you're only upgrading for scalability reasons. SQL Server licences are

> not

> cheap, if this is your only reason.

> 

> MySQL is a controversial piece of software, and because of it's lack

> of

> support for things like stored procedures, triggers and (most

> importantly)

> transaction management and rollback, it has even been accused of being

> no

> more than a file management system with an SQL interface. However, if

> you

> are not planning on using transactions, triggers or stored procedures,

> 

> mySQL may well be enough. Because of its simplicity, in fact, it can be

> 

> dazzlingly fast. While I would hesitate to run an e-commerce site off

> it

> yet, because of it's lack of transactions (although some PHP sites do),

> I 

> would certainly consider it as a first replacement for Access. ODBC 

> drivers exist for it, just like any other database manager and the 

> essentials of connecting to it and running queries against it are just

> 

> like using any other SQL database in ASP. It lacks Access's GUI, but if

> 

> your database structure is fairly straightforward this wil not be too 

> much of a problem - remember that once your table structure is in place,

> 

> you will be able to link an access database to them and actually perform

> 

> the data entry via that, using an interface you already know.

> 

> If it's any encouragement, the whole of the P2P website's frontend

> runs

> off a mySQL database. For read-only or read-and-append type work, I

> would 

> seriously consider mySQL, rather than paying out for SQL Server. If you

> 

> start to find yourself modifying records in multiple tables

> simultaneously

> then it obviously won't do, and you'll need SQL Server or Oracle (or,

> of

> course, Postgre SQL if you still want to avoid the software licenses -

> 

> although it has a reputation for being slow).

> 

> Just a thought.

> Daniel Walker

> Wrox Press

> 

> > Please help me...

> > Any input is good input =)

> > 

> > I'm have Microsoft Access 2000, SQL Server 2000 (trial version) and 

> > running everything on Windows 2000 Professional.

> > 

> > I have completed a fully functional ASP website using Access 2000 as

> 

> the 

> > database program.  I now need to switch over to SQL Server...where do

> i 

> > begin?

> > 

> > for starters...do I export the database from Access into SQL or import

> 

> > Access file from SQL?  I've read Access 2000 and SQL 2000 has some 

> > conflicts, do I need to download a service pack from

> microsoft.com/sql

> > ...if yes which of the 3 parts of service pack 1 do i need?

> > 

> > Which "type" of database should i set up...server/client or front end/

> 

> > back end?  I read that with the front end/back end option, I can reuse

> 

> my 

> > FORMS in Access and link the tables to SQL.  How the heck do I do

> this? 

> > HOW THE HECK DO I ACTUALLY IMPORT SOMETHING?

> > 

> > SQL seems intimidating...nothing like Access.  I'm lost of where to 

> > start.  Tried importing tables in SQl but SOOO many options to choose

> 

> > from...confusing...SQL said successfully completed conversion but I 

> have 

> > no idea where the file is on my computer???

> > 

> > If you have any guidance to any parts of the above, please tell me

> =P

> > 

> > Thank You in advance

> > Kien

> > 

>

Sounds like mySQL would be ideal, then - although there's no import

facility! ;)



From you description, it does not sound like you need SQL Server yet. In

fact, you could probably store most of what you need in just one table, by

the sounds of it.



By Access's GUI I mean the user interface. To create tables and give them

columns can still require command line instructions, although I believe

mySQL are working on providing a Graphical User Interface. Wrox is 

bringing out a MySQL book soon, but the actual mySQL manual is down-

loadable from the maker's website along with the product and should get

you started - and there's always ists, of course. Like I say, once the

database is constructed, you can open a database in Access and select to

link to the mySQL database from it. Then you can feed data directly into

the MySQL database from your Access one (be aware, though, that any

changes will have immediate effect on your database, and consequently the

site itself).



As for scalability... Well, it's not crippleware, like Access, so there is

no hard and fast figure that anyone can quote and there haven't been any

ASP-based benchmark tests that I know of. However, if you look at the

top of the P2P front page, http://p2p.wrox.com (where it says "you are

one of the x-number of people browsing this site") you'll see how many

active user sessions the site is supporting (sessions have a ten minute

timeout on this site). The figure should be about 100-150 at this time of 

day, but it has been up to about 4 or 500, on some occasions.



Daniel Walker

Wrox Press



> Thanks Daniel

> 

> My entire ASP website is read only except for one aspect...changing 

user 

> password which only involves manipulation of one table. 

> 

> Licensing SQL Server is not an issue since the place i work for will 

eventually 

> get it sooner or later if not for this project.

> 

> I'm just getting started with SQL server so I have no idea what 

transactions, 

> triggers or stored procedures are.

> My webpage is almost like a library catalogue...search for article by 

author or 

> key word search and download corresponding pdf files.  From this 

description, 

> do you think I need the the options you mentioned before?

> 

> What is "Access's GUI", my table structure is fairly simple.

> 

> Lastly, what is the maximum concurrent user mySQL can support?...this 

is the 

> main reason why I'm switching out of Access to begin with.

> If mySQL support what I'm trying to do...then definitely i'll give it a 

shot.

> 

> Thanks

> Kien

> 

>

Sorry Daniel I have a stupid question to ask you.



what do i exactly download from mysql.com?

I'm using windows 2000 professional, ibm pentium processor 266

there are SOO many choices to pick from



Thanks

Kien

What you probably want is at:



http://www.mysql.com/downloads/mysql-3.23.html



Not the tidiest webpage in existence, I'll grant you! The Unix-based 3.32.40 versions are

listed first, a Windows version for this isn't available yet, so you have to scroll down to 

where it says "Older and contributed binary (tarball) distributions" (a "tarball" is just a 

Unix word for a zip file - in fact a zip file _is_ a tarball, strictly speaking). You'll see that 

the Windows version 3.23.38a (the one they recommend at the top of the page)  is the 

first one listed. 



While you're there, download the MySQL manual, and get it printed out - or at least the 

bits you'll need to get started.



Dan



> Sorry Daniel I have a stupid question to ask you.

> 

> what do i exactly download from mysql.com?

> I'm using windows 2000 professional, ibm pentium processor 266

> there are SOO many choices to pick from

> 

> Thanks

> Kien