Dear LLBLGEN Team,

I want to tell thank you for creating such a tremendous product! We have a Silverlight 4 RIA application that was using an Oracle databases for data and ASP.NET services. Our databases contained about 30 tables, approximately 600 fields, and a lot of RIA attributes. Today, in less than two hours, I successfully migrated our application from Oracle to SQL Server, and upgraded to Silverlight5! Although I was familiar with your LLBLGEN Pro tool, I have never performed this kind of migration. I am very happy to report that the process was logical and I didn't even have to refer to your documentation!
Here is a summary that may be helpful for others...

I added our SQL Server database to the Catalog Explorer. For each entity in the Relational Model, I did the following:

1) Selected the SQL Server Database Type; 2) Created a mapping by clicking "Create mapping"; 3) I quickly adjusted the .NET Types and removed Oracle Sequences; 4) I saved my changes; 5) I selected the Oracle Database Type; 6) I removed its mapping; 7) I saved my changes;

After completing these changes for all of our Entities, I performed a Validate, and it detected a minor issue. Next, I did a validate and Adjust, no issues... Finally, I generated our DAL projects. In our VS2010 project, I simply replaced SD.LLBLGen.Pro.DQE.Oracle.NET20 with SD.LLBLGen.Pro.DQE.SqlServer.NET20. I removed "using" statements for Oracle. I adjusted our web.config to use SQL Server rather than Oracle.

Et voila! I rebuilt and ran our application! All I can say is WOW!!!

What I expected to take 2-3 days is done and now I can enjoy the holidays!!!

Thank yoU!

Mike

Great to hear it was a smooth transition

Btw, there's a build-in auto-map feature, which might have auto-mapped the entities to the SQL Server DB for some entities if the table names were equal to the entities: - Add the SQL Server database to the project - Right-click 'entities' and click 'Auto-map unmapped entities', which will create a new mapping for each entity onto an existing or new table in a database if it's not already mapped to an element in that database. - Validate

But in case where the entities are named differently than the target tables, the auto-mapped won't find the proper table to map to and will create a new one. So it might indeed be the way you did it is the fastest .

Happy holidays, Mike