Comments on: LINQ to SQL and Database Schema Sync http://blogs.rev-net.com/ddewinter/2008/02/16/linq-to-sql-and-database-schema-sync/ A Developer's Melting Pot Tue, 06 Jan 2009 21:32:42 +0000 http://wordpress.org/?v=2.6 By: David DeWinter » Blog Archive » DBML Fixup Preview http://blogs.rev-net.com/ddewinter/2008/02/16/linq-to-sql-and-database-schema-sync/#comment-696 David DeWinter » Blog Archive » DBML Fixup Preview Mon, 25 Aug 2008 03:41:49 +0000 http://dev.rev-net.com/blog/ddewinter/?p=41#comment-696 [...] in February I blogged about DBML Fixup—a tool whose goal was to sync LINQ to SQL models with their [...] [...] in February I blogged about DBML Fixup—a tool whose goal was to sync LINQ to SQL models with their [...]

]]> By: Kris http://blogs.rev-net.com/ddewinter/2008/02/16/linq-to-sql-and-database-schema-sync/#comment-622 Kris Thu, 31 Jul 2008 05:48:39 +0000 http://dev.rev-net.com/blog/ddewinter/?p=41#comment-622 Hi David, I added a pile of new functionality to the add-in so it now supports new/dropped tables, new/dropped/modified columns, new/dropped FKs and will update the dbml accordingly. Stored procs are not part of the synchronization yet but I'm planning it in a future update. I moved the download out of my blog onto a separate page: http://www.huagati.com/dbmltools/ and split it into three editions; free, standard and pro. The standard and pro editions has a small license fee attached to them to pay for continued development but the fee should soon pay itself back for the time saved on not having to make apply all db changes to the dbml by hand... Hi David,

I added a pile of new functionality to the add-in so it now supports new/dropped tables, new/dropped/modified columns, new/dropped FKs and will update the dbml accordingly. Stored procs are not part of the synchronization yet but I’m planning it in a future update.

I moved the download out of my blog onto a separate page: http://www.huagati.com/dbmltools/ and split it into three editions; free, standard and pro. The standard and pro editions has a small license fee attached to them to pay for continued development but the fee should soon pay itself back for the time saved on not having to make apply all db changes to the dbml by hand…

]]> By: David DeWinter http://blogs.rev-net.com/ddewinter/2008/02/16/linq-to-sql-and-database-schema-sync/#comment-445 David DeWinter Tue, 08 Jul 2008 12:54:50 +0000 http://dev.rev-net.com/blog/ddewinter/?p=41#comment-445 Tim, good to hear from you again. I'll have a look at LLBLGen Pro and see what I can find. Kris, thanks for the heads up as well as the add-in. I was wondering how to get around an issue in my own work, but your code provided some good leads. :) Tim, good to hear from you again. I’ll have a look at LLBLGen Pro and see what I can find.

Kris, thanks for the heads up as well as the add-in. I was wondering how to get around an issue in my own work, but your code provided some good leads. :)

]]> By: Kris http://blogs.rev-net.com/ddewinter/2008/02/16/linq-to-sql-and-database-schema-sync/#comment-437 Kris Tue, 08 Jul 2008 03:05:15 +0000 http://dev.rev-net.com/blog/ddewinter/?p=41#comment-437 I have written an add-in for synchronizing simple changes (added/removed fields, removed tables) from the db to the dbml. I also have an add-in for enforcing naming conventions, however it only supports lowercase_underscore_separated_names to UppercasePascalNames. Anyway, it is related to what you are describing so you may want to take a look at it at blog.huagati.com I have written an add-in for synchronizing simple changes (added/removed fields, removed tables) from the db to the dbml. I also have an add-in for enforcing naming conventions, however it only supports lowercase_underscore_separated_names to UppercasePascalNames. Anyway, it is related to what you are describing so you may want to take a look at it at blog.huagati.com

]]> By: Tim Clark http://blogs.rev-net.com/ddewinter/2008/02/16/linq-to-sql-and-database-schema-sync/#comment-351 Tim Clark Wed, 18 Jun 2008 19:17:49 +0000 http://dev.rev-net.com/blog/ddewinter/?p=41#comment-351 Hi David, Sounds like you are really getting deep! But that is only expected from a Neumont graduate :). http://www.llblgen.com/defaultgeneric.aspx is an OR mapper that supports LINQ to SQL and also handles synchronization from the DB to the DBML file by completely regenerating the DBML file for you. Thing is it has a way of retaining your custom changes to the DBML file I think through the use of specifically named #Region tags. It pulls them out generates and then reinserts them, well this is what I have been told, I haven't tried it out myself of looked into it all that deep. Though you might want to take a look at it and see how they do it and then implement that into your extension of the VS designer. Let me know what you find out... Hi David,

Sounds like you are really getting deep! But that is only expected from a Neumont graduate :). http://www.llblgen.com/defaultgeneric.aspx is an OR mapper that supports LINQ to SQL and also handles synchronization from the DB to the DBML file by completely regenerating the DBML file for you. Thing is it has a way of retaining your custom changes to the DBML file I think through the use of specifically named #Region tags. It pulls them out generates and then reinserts them, well this is what I have been told, I haven’t tried it out myself of looked into it all that deep. Though you might want to take a look at it and see how they do it and then implement that into your extension of the VS designer. Let me know what you find out…

]]> By: Kate http://blogs.rev-net.com/ddewinter/2008/02/16/linq-to-sql-and-database-schema-sync/#comment-203 Kate Fri, 28 Mar 2008 07:12:00 +0000 http://dev.rev-net.com/blog/ddewinter/?p=41#comment-203 Hi David, You are quite right, Database Restyle only propogates changes from LINQ To SQL Model to the database. ;-) Just in case, if you ever think about doing this, you will aleady know that such functionality is implemented. Kate. Hi David,

You are quite right, Database Restyle only propogates changes from LINQ To SQL Model to the database. ;-) Just in case, if you ever think about doing this, you will aleady know that such functionality is implemented.
Kate.

]]> By: David DeWinter http://blogs.rev-net.com/ddewinter/2008/02/16/linq-to-sql-and-database-schema-sync/#comment-202 David DeWinter Tue, 25 Mar 2008 14:31:57 +0000 http://dev.rev-net.com/blog/ddewinter/?p=41#comment-202 Hi Kate, I had not heard of the Database Restyle tool, but I did look into briefly this morning. My understanding is that it helps you propagate changes from your LINQ to SQL model to your database, but not the other way around. Is this correct? I think it would be a useful tool, but it is not quite the same path I'm going down. David Hi Kate,

I had not heard of the Database Restyle tool, but I did look into briefly this morning. My understanding is that it helps you propagate changes from your LINQ to SQL model to your database, but not the other way around. Is this correct?

I think it would be a useful tool, but it is not quite the same path I’m going down.

David

]]> By: David DeWinter http://blogs.rev-net.com/ddewinter/2008/02/16/linq-to-sql-and-database-schema-sync/#comment-201 David DeWinter Tue, 25 Mar 2008 14:29:12 +0000 http://dev.rev-net.com/blog/ddewinter/?p=41#comment-201 Hi boomhauer, It is possible that code generation techniques can be used (like Mygenerationsoftware or CodeSmith) for generating code that the LINQ to SQL provider can use to query a database, but that is not really what I'm going for. The developer customizations I'm trying to preserve are at the .dbml level (mainly by "enhancements" to the designer). Consequently, the code generation layer will stay the same, but the mapping layer will be enhanced. Thanks also for mentioning the scenario you have to undergo every time you want to make updates. It's something I'll note down. David Hi boomhauer,

It is possible that code generation techniques can be used (like Mygenerationsoftware or CodeSmith) for generating code that the LINQ to SQL provider can use to query a database, but that is not really what I’m going for. The developer customizations I’m trying to preserve are at the .dbml level (mainly by “enhancements” to the designer). Consequently, the code generation layer will stay the same, but the mapping layer will be enhanced.

Thanks also for mentioning the scenario you have to undergo every time you want to make updates. It’s something I’ll note down.

David

]]> By: Kate http://blogs.rev-net.com/ddewinter/2008/02/16/linq-to-sql-and-database-schema-sync/#comment-200 Kate Tue, 25 Mar 2008 03:40:05 +0000 http://dev.rev-net.com/blog/ddewinter/?p=41#comment-200 Hi David, Have you heard about a new database synchronization tool Database Restyle (http://www.perpetuumsoft.com/Product.aspx?lang=en&pid=55) that supports LINQ To SQL object model and allows automatic synchronization of LINQ To SQL model with your live database? Probably, this tool will be helpful. Hi David,

Have you heard about a new database synchronization tool Database Restyle (http://www.perpetuumsoft.com/Product.aspx?lang=en&pid=55) that supports LINQ To SQL object model and allows automatic synchronization of LINQ To SQL model with your live database? Probably, this tool will be helpful.

]]> By: boomhauer http://blogs.rev-net.com/ddewinter/2008/02/16/linq-to-sql-and-database-schema-sync/#comment-199 boomhauer Tue, 25 Mar 2008 01:30:16 +0000 http://dev.rev-net.com/blog/ddewinter/?p=41#comment-199 Could much of this be performed via the mygenerationsoftware.com code gen framework? via some fancy templates? yes i need this right now as well. my requirements are a bit different though - i have a lot of associations created in the dbml file which dont exist in the actual db. So if i delete and reimport them, the assocs are lost and have to be hand created. do this with 50 assocs and you get the pic ;) Could much of this be performed via the mygenerationsoftware.com code gen framework? via some fancy templates?

yes i need this right now as well. my requirements are a bit different though - i have a lot of associations created in the dbml file which dont exist in the actual db. So if i delete and reimport them, the assocs are lost and have to be hand created. do this with 50 assocs and you get the pic ;)

]]>