Re: ASP - converting to SQL server

by Mikael Bystr=?ISO-8859-1?Q?=f6m?= <sunergy(at)mac.com>

 Date:  Sun, 28 Oct 2001 12:55:20 +0100
 To:  "hwg tech" <hwg-techniques(at)hwg.org>
  todo: View Thread, Original
Jeff Nelson enlightened us on 01-10-28 02.58 with this:

>Sure. Unless your database design is *very* simple, avoid the up-sizing 
>wizard. Instead, use the Data Transformation Services in SQL Server. 
>Basically, this will import your Access data into your SQL Server 
>database. Very easy.
>
>It bears mentioning that coming from an Access background, one needs to 
>adopt a new way of thinking about databases. First, with Access, your 
>database was contained within a single file (ourfile.mdb for example). 
>With SQL Server, your database is tied to your server in many files. In 
>other words, you are unable to merely copy your database to another file 
>and install it on another computer as you would with an .mdb file. Second, 
>you have a security context with SQL Server that is not available in 
>Access. And third, you have many issues such as data types, stored 
>procedures, relationships, triggers, etc. that are separate issues in 
>themselves.  


This was great advise. Thanks, Jeff.

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA