This is a migrated thread and some comments may be shown as answers.

Update db schema - new open access

3 Answers 52 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
Saene
Top achievements
Rank 1
Saene asked on 04 Oct 2011, 09:00 AM
Hi there,

with the "new" version of openaccess, how should i update database schema on client side?

With the classic open access, i used to use vschema, specifying the assembly, config file and so on...

But it does not seem to work for the new OA. I've read the Deployement and update consideration here, which seems to be for both versions (classic and new), and which explains that we have to use vschema, however, following the link about vschema brings your here, and it seems to handle only classic OA.
Am I right?

So now, what is the good practice for updating database schema on client side (I don't know the exact updates to apply to the db, as I don't know when the last installation was done). Can I still use vschema? Is there any other way to do that?
Thanks a lot for your answers,

Antoine.

3 Answers, 1 is accepted

Sort by
0
PetarP
Telerik team
answered on 06 Oct 2011, 03:57 PM
Hello Saene,

 Using the vschema in command line mode will only work with the old mapping. Unfortunately I cannot provide you with a way to make it work because the representation of the metadata and thus the way it is read from a compiled assembly is different between the old and the new mapping.
Would it be possible for you to use the update database wizard that comes with the designer in order to generate a full database definition script? Later you can execute that script on your client machine and thus create the database. Additional information on the update database wizard can be found in our online documentation here.
We are looking forward to your reply.

Greetings,
Petar
the Telerik team

Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>

0
Saene
Top achievements
Rank 1
answered on 19 Oct 2011, 10:13 AM
Hi Petar,

thanks for your answer.
I understand that vschema only works with the old mapping.
However, the solution you suggest aims to create a database creation script and deliver it to the client. This forbids installing a new version of the software and migrating the db and the data it contains.
I absolutely need a way to upgrate the database on the client computer, just as the vschema did with the old mapping.
I cannot believe that anybody never had this need before me!

Anyway, thanks a lot for any advice you could give,

Antoine.
0
PetarP
Telerik team
answered on 19 Oct 2011, 03:31 PM
Hello Saene,

 I cannot quite understand what is wrong with executing either the update or create script on the client machine ones your software is installed? 
If this is a high priority for you we will certainly discuss the possibility of improving the vschema to work with newer models.

Best wishes,
Petar
the Telerik team

Check out the latest stable build of Telerik OpenAccess ORM. Download it and benefit from our new Project Templates.

Tags
General Discussions
Asked by
Saene
Top achievements
Rank 1
Answers by
PetarP
Telerik team
Saene
Top achievements
Rank 1
Share this question
or