Indra77
asked on
Converting MS ACCESS DATABASE TO SQL DATABASE.
Hi There,
I need few more information on this topic for converting the access db to ms sql db.
When i went through the information on using upzing tool and DTS in sql server, i found few different option available, which make me confuse.
I used MS ACCESS upsizing tool to convert only table defination and structure, relation ship etc,
and DTS in sql server to import data in existing database created with upsizing tool.
below is the few information i need.
- should i use trigger or DRI for table relationship
-should i use upsing tool for complet importing of table defination as well as data or upzing only for table defination, relationship and DTS for data.
-when converting application there are three option,
1.- no application change
2. Link sql server table to existing application
3. create a new access client/server application
keeping in mine that we want to use our existing front end after moving to sql server.
after i move data what and how i can use the exising front end, as i have not done this before, i really need information.
i already move data to the sql server, but this is only testing database. please give me brief information how can i move, configure to use existing front end.
Thanks.
Converting MS Access database to the SQL...
I need few more information on this topic for converting the access db to ms sql db.
When i went through the information on using upzing tool and DTS in sql server, i found few different option available, which make me confuse.
I used MS ACCESS upsizing tool to convert only table defination and structure, relation ship etc,
and DTS in sql server to import data in existing database created with upsizing tool.
below is the few information i need.
- should i use trigger or DRI for table relationship
-should i use upsing tool for complet importing of table defination as well as data or upzing only for table defination, relationship and DTS for data.
-when converting application there are three option,
1.- no application change
2. Link sql server table to existing application
3. create a new access client/server application
keeping in mine that we want to use our existing front end after moving to sql server.
after i move data what and how i can use the exising front end, as i have not done this before, i really need information.
i already move data to the sql server, but this is only testing database. please give me brief information how can i move, configure to use existing front end.
Thanks.
Converting MS Access database to the SQL...
ASKER
Do i have to change any things in term of configuration on different machine and on server using this database when i use second option, link sql server table to existing application.
As i read on a book saying using DRI for relation is not very good, can you give me bit more explaination.
If i want to go for option 3 in case of application change, what i need to do to able to access our front end from different computer.
Thansk.
As i read on a book saying using DRI for relation is not very good, can you give me bit more explaination.
If i want to go for option 3 in case of application change, what i need to do to able to access our front end from different computer.
Thansk.
As i read on a book saying using DRI for relation is not very good, can you give me bit more explaination
Which one ?
Refering to here: (Discussion on this topic -- 2002)
http://www.dbforums.com/archives/t317082.html
It is also possible that triggers are used for various taks -- but it does depend what DRI tasks you are looking to perform in a transaction-- Generally use the FKs/PKs inbuilt constriants if possible, than using triggers they are a lot easier to debug and consume less memory resources in checking for the same task.
Which one ?
Refering to here: (Discussion on this topic -- 2002)
http://www.dbforums.com/archives/t317082.html
It is also possible that triggers are used for various taks -- but it does depend what DRI tasks you are looking to perform in a transaction-- Generally use the FKs/PKs inbuilt constriants if possible, than using triggers they are a lot easier to debug and consume less memory resources in checking for the same task.
ASKER
Hi There,
As i am on the testing phase of data migration. I need small information. Once i update or migrate our database to sql server. I want to have synchronization between .mdb FILE AND DATA IN SQL SERVER. Is it possible to do this. I need this one for few month so that i can build for or other necessary things to use .adp and sql server.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
* better to use DRI than a trigger, trigger consumes memory and has a higher overhead than a DRI.
-should i use upsing tool for complet importing of table defination as well as data or upzing only for table defination, relationship and DTS for data.
* It would be better to use the tool, if it fails then use DTS.
-when converting application there are three option,
1. no application change
2. Link sql server table to existing application
3. create a new access client/server application
* Personally in this situation I would link sql server table to existing application.
If linking the tables, all the objects (Forms/Reports etc) just need to point to the linked tables, the table is stored in sql-server (the only main difference) but access can use the table as if it was still in the local database system.
It should remain compatible without any back-end access problems, if the table names are the same as they were originally within MS Access.