ஒரு பார்வை

Normalizing Your Database

• A table should store only data for a single type of entity.
• A table should avoid nullable columns.
=========

what is normalization? Basically, it’s the process of efficiently organizing data in a database.
There are two goals of the normalization process: eliminate redundant data (for example, storing the same data in more than one table) and ensure data dependencies make sense (only storing related data in a table).

______
CAPital

How to Migrate from Access 2002 to SQL Server 2000

http://www.microsoft.com/technet/prodtechnol/sql/2000/Deploy/accessmigration.mspx

============================

Migrating Your MS Access Database to MS SQL Server 7.0

http://www.microsoft.com/technet/prodtechnol/sql/70/deploy/access.mspx

[detailed explanation of migration of Queries]

_____
CAPital

Access databases often have a flat structure, that is, there are few tables and many fields in each table. Access works efficiently with tables containing many fields and fewer joins between tables, whereas SQL Server works more efficiently with narrower tables containing fewer fields and more relationships between tables. Combined with properly used indexes, you will see a vast improvement in database reads and updates, because SQL Server is efficient at selecting rapid, efficient joins between tables.
http://www.microsoft.com/technet/prodtechnol/sql/2000/Deploy/accessmigration.mspx#EBAA

=======================

• A table should store only data for a single type of entity.

Attempting to store too much information in a table can prevent the efficient and reliable management of the data in the table.

• A table should avoid nullable columns.

Tables can have columns defined to allow null values. A null value indicates that there is no value. Although it can be useful to allow null values in isolated cases, it is best to use them sparingly because they require special handling that increases the complexity of data operations. If you have a table with several nullable columns and several of the rows have null values in the columns, you should consider placing these columns in another table linked to the primary table. Storing the data in two separate tables allows the primary table to be simple in design but able to accommodate the occasional need for storing this information.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/createdb/cm_8_des_02_2oby.asp

_____
CAPital

Source: http://kb.seekdotnet.com/ViewArticle/33data.aspx

1. From the Start Menu, select Programs -> Microsoft SQL Server -> Import and Export Data then click Next.
   
2. In the Source Server field, type in the Name or IP of the source server (your server), choose Use SQL Server Authentication, type in your username and password, choose your database from the “Database” field, click Next.
   Note: You can also use Windows Authentication if the SQL server is a local server.
   
3. In the Destination Server field, type in the hostname of the SeekdotNet SQL Server (this is listed in your hosting control panel), choose Use SQL Server Authentication, type in your SeekdotNet database username and password (this was sent in your database order confirmation email), choose your database from the Database field, click Next.
   
4. Choose Copy Tables and Views, Choose the table that you like to export…, click Next.
   
5. Leave next window as is, click Next.
   
6. Click Finish.