The syntax of the SQL the DataSet Design Surface generates

Hot Topic

Help with pointing to an image!
Integrated Security...
creating users in sql eypress
Query Performance
Trouble using XML Source from a variable
Database Sort Order / Collation
Stored Procedure being saved in System Stored Procedures
SSIS thinks an invalid expression is valid
"Open Table" NOT WORKING in Management Studio
Need a list of Error Code

SQL Server

Still need LOB at the end of a dataset?
Data Transformation: copying a table to a table... How does it work?
How to Fetch the Recrods from MS Access and using it in Script Task Using Control Flow Tools(Execute SQL Task)
Using a Parameter for ORDER BY Clause
How to bind the table columns dynamically
SQL Server 2005 Standard Installation Problem
Retieving ODBC Settings.
Connectivity issues
Logging of SSIS package doesnt work when executed as a job
Restricting Access to Management Folder under SQL Server 2000

The syntax of the SQL the DataSet Design Surface generates

I'd like to design my dataset's in VS2005 in such a way that I develop at design-time using SQL2005, however I'll have the option of replacing the connection, sqladapter and command objects in the generated source code with another database's (like mysql, etc.)

Since the schemas are identical across the different database kinds, the key here is making sure that the generated SQL is ANSI compliant.  Right off the bat the square brackets around table names cause problems.  Is there anyway to tell VS2005 to use the ANSI compliant quotes instead

Thanks

Answer this question

The syntax of the SQL the DataSet Design Surface generates

  • aping

    I agree with you - I have looked at many of these tools in the past.  However, none of these object mapping tools replace the client side filtering capabilities of datasets.

    AFAIK, the only one that supports client side filtering is Deklarit and that's because they specifically build up on the .NET datasets instead of writing a whole new container layer.

    A lot of the apps I write need a disconnected processing ability, ie load the data from the db and then perform a lot of data processing (here is where the filtering comes in handy) and then return a processed dataset for the client to consume.

    Traditionally this logic is taken care of in stored procedures, however I'd like to stay cross-db, so I'd like to implement it at the .NET code layer with as little calls as possible to the db.

  • DavidDawkins

    I am trying to find out your current email address, as I am tavelling to Turkey in mid May and would like to meet you

  • EmSOFT

    Josh,

    thanks for your recommendation.  I wasn't aware of the client side filtering capabilities of llblgen pro.  I'll definitely take a look.

  • MA Tester

    Check out LLBLGen Pro.  It is built on data tables, and client side filtering with their EntityCollections is pretty smooth.  We even use their business objects and collections in our bound forms and grids (even filtered ones) without any problem.  Cross-db is automatic.  We tried going down the dataset route and just couldn't make it work for our needs, this was the closest we could find that was also easy to use and supported.

    Josh

  • jskim

    Rather than use typed datasets, I'd suggest using a good OR/M tool such as LLBLGen Pro (www.llblgen.com) or NHibernate (http://sourceforge.net/projects/nhibernate).  NHibernate is free, but we've found LLBLGen Pro to be far easier to implement.

    Best of Luck,
    Josh Lindenmuth

  • The syntax of the SQL the DataSet Design Surface generates
Answer this question