I am aware similar questions have been asked in the past but they were based on older versions of llblgen.

What is the best course of action if I am developing a web application with llblgen (version 2.6) initally working off a Sybase ASE database and then in a few months working off SQL Server 2005 database? The database schema are identical in both Sybase and SQL Server.

A Possible solution is: Create a llblgen project and generate the DAL using the Sybase database and use it with the web application. Then when ready to use SQL Server database, create a new llblgen project and generate the DAL using SQL Server database. After generating the DAL simply replace the DAL dll in the web application project?

Is above correct? Is there better solutions to this class of problems?

Is there a difference using self servicing as opposed to adapter.

I am using LLBLGen Pro 2.6 Final self servicing two class and C#.

It's doable. I had done it before and it's smooth. These are some recommended steps:

1) Use "project converter" (available in customer area) to convert from asa project to sqlserver. This will generate a new SQLServer LLBLGen project. The benefits is that you don't lose any custom changes you did in the ASA project. 2) Load sqlserver project (thus the conversion result) 3) In case you don't have the SQLServer DB yet, you can use the DDL SQL templates (available from the website in the customer area) to generate a DDL SQL schema for the sqlserver db. 4) Generate code from the sqlserver project. 5) Compile and release your new dll. Remember that now your DAL references SQLServerDQE and not the old AsaDQE. Needless to say: all namespaces, entity names, indentity fields, typeconverters, etc. must be exactly the same as the old project.

Now, Adapter is better for this kind of things. If you have custom code on your entity classes or you have another kind of customization, in Adapter you just need to replace the DBSpecific project. But it works for SelfServicing as well, it's just that you have to migrate your entities or your custom code.