Access data base to SQL Server managment

[BoSCHoW]

Hi all,

I have a data base made in MS access and i wanted to know if it is possible to import it into MS SQL server management. If it is possible could somebody write an example, from which i can learn how do i do that?

Thank you for your time and help
Best regards,
BoSCHoW.

 

[SQLBI]

Use the 'Upsizing Wizard' to convert your .mdb file to a .adp (Microsoft Access Project) file.

This will upgrade your Access DB to a SQL Server DB.

Check out Aceess Projects and Upsizing in the help files or on the web for more information.

Hope this helps.

Cheers,
Leigh

The problem with common sense is that it isn't that common!

 

[Catadmin]

Or you could import the data using the SSIS Import / Export Wizard. Create a new DB in SSMS, right click the DB and choose All Tasks -> Import.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[BoSCHoW]

Hi all,

i wanna thank for this valuable informations. I tried and it worked. But while searching how to migrate access database
i found out than i can link it as well. Whats the difference between migration import/export a database to a server and link a database to a server? When is better to use a link method and when is better to use a migration method? And what are the advantages/disadvantages of the migration method? What are the advantages/disadvantages of the link method?

Thanks again for your time and help,
best regards
BoSCHoW.

 

[Catadmin]

It depends on your situation.

Linking a database leaves the linked DB in its original format, but requires a persistant network connection to that linked DB in order to use it. Plus there may be performance overhead issues.

Upgrading a database can change datatypes and alters the meta data for the DB so you can NEVER revert back to an Access DB. You'd have to export the data to a new Access DB and set up all your macros, reports, etc. all over again in order to get it back. However, the performance overhead becomes nil because SQL doesn't have to constantly make calls to another DB to get the information it's looking for.

If people are going to continue updating the Access DB after this change, you need to make it a linked DB. Otherwise, consider upgrading the DB to SQL.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[BoSCHoW]

Hi all,

Now i want to ask you the following question if it is possible to monitor values, from lets say a kontroller with the SQL server that has the database of the controller parameters. I want to show this parameter values in excell ... In short i want to make a SCADA "supervision system" that can show values with excell.

Thanks for your time and help.
Best regards
Bostjan.

 

[Catadmin]

<blink> Um, you mean you want to monitor permissions & roles in the database and export it to Excel?



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[BoSCHoW]

Lets say that i want to monitor a single value, that is constantly changing. I want only to export this single address
to excel and monitor it . .. Do you think this thing is possible ?

 

[Catadmin]

If you want to monitor a piece of data in the SQL Server, then no, it's not possible the way you describe it.

The only possible way I know of to do this is to actually create an auditing trigger on the table in question, which stores all the values, new & old, in a new table, which you could then create a report for.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"