1) The objectQualifier is useful when you are given a single database in a shared SQL hosting environment, which is very common with entry level providers. Although many of us can afford the $2500 to $25,000+ SQL server license, many students and hobbyists still use a shared license.

To my knowledge, LINQ does not handle dynamic table names to support the objectQualifier at this time, and we really don’t know if it will in the future. You can hard code the actual table names including the objectQualifier but the code is not portable to other DNN installations. You need to replace all of the table names and recompile.

I would not recommend removing the objectQualifier from DNN as it would break existing installations. It only takes about an hour to remove an objectQualifier manually if you want to try it on a duplicated, backup up database.

I challenge the DNN community to write a SQL script to remove the objectQualifier automatically by renaming tables, stored procs, and a few views.

2) There is nothing easier than SQL Server Management Studio to create your database and tables using a graphical interface. When you have constructed your schema, you simply right click on the table and select script table|create and you can view the script needed to create your table. You can learn basic create table scripts in about 10 minutes.

LINQ is not a replacement for SQL, it simply maps to an existing SQL structure/schema.