Re: Copy database schema from Access to SQL Server

I still don't know why you're reinventing the wheel. I would leverage the considerable work done by Microsoft when it created SSIS. It can import a JET database in a single stroke. It's programmable, can run on a schedule and is very fast.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------

<schneider@xxxxxxx> wrote in message news:1193292855.440585.215650@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On 24 Okt., 15:26, Paul Clement
<UseAdddressAtEndofMess...@xxxxxxxxxxxxxx> wrote:
On Wed, 24 Oct 2007 02:16:37 -0700, schnei...@xxxxxxx wrote:

¤
¤ If you're talking about the Wizard in MS Access to convert single
¤ projects to SQL Server, this won't work for me. I need to
¤ programatically copy the database schema. I think the key issue is "Do
¤ I have to dynamically create DDL SQL statements for each element I
¤ want to copy to SQL Server or is there a simpler solution?" Using C#
¤ is mandatory.

The easy method is to use the wizard. If you want to use code then you will have to read the Access
schema and then use DDL code to create the corresponding objects in SQL Server.

Paul
~~~~
Microsoft MVP (Visual Basic)

Thanks for your response. It seems like I have to parse the complete
template database and the target database and compare their schemata.
For differing elements, I will have to create a DDL statement as you
suggested.
My last resort was a solution like it was possible with dao, as you
could parse through the tabledef, relations, ... collections and apply
the changes directly. However, as OleDb and SqlClient seem to differ
very much in the way they treat constraints and other concepts,
sticking back to basic DDL code seems the best solution. Furthermore,
maybe sometimes Oracle or another database solution comes into play
and using DDL code I will have less trouble integrating it into my
app.
Anyway, thanks for your help Bill and Paul. You pointed me in the
right direction.

Regards,
Hannes

.

Relevant Pages

  • Re: Access (jet) vs SQL Server Express
    ... ¤ Access or SQL Server Express. ... more robust database server package. ... Microsoft MVP ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: What Database model should I use?
    ... I'm not sure which SQL Server I'm going to convert to ... ... I'm currently converting the application to VB6 ... > ¤ I have been programming in microsoft access for years. ... upgrade the JET engine to a real SQL database, ig SQL Serever, Orical, MySQL ...
    (microsoft.public.vb.database)
  • Re: Upload Access Data to Web
    ... to set up a connection between the Access Database and Sql Server? ... Access Database already exist but since the Sql Server Database hasn't been ... ¤ local server to a sql table on a web server. ...
    (microsoft.public.vb.com)
  • Re: Copy database schema from Access to SQL Server
    ... ¤ projects to SQL Server, ... schema and then use DDL code to create the corresponding objects in SQL Server. ... template database and the target database and compare their schemata. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Copy database schema from Access to SQL Server
    ... ¤ projects to SQL Server, ... The easy method is to use the wizard. ... schema and then use DDL code to create the corresponding objects in SQL Server. ...
    (microsoft.public.dotnet.framework.adonet)
Loading