OleDb different DataBases
-
Hi as you know with OleDB we can open many kind of DataBases. i want to know is there any difference between SQL statements we send to darabases or all of them support support a single tyoe of SQL statements. I wanted to Get Information of tables of Databases(something like "Server Explorer" of VS.NET which opens every Type of Databases and shows their "Tables" and "Queries" and "procedures" and "Functions". abd also Field Types) can i do it with SQL statement? and if yes are they different for different databases?
-
Hi as you know with OleDB we can open many kind of DataBases. i want to know is there any difference between SQL statements we send to darabases or all of them support support a single tyoe of SQL statements. I wanted to Get Information of tables of Databases(something like "Server Explorer" of VS.NET which opens every Type of Databases and shows their "Tables" and "Queries" and "procedures" and "Functions". abd also Field Types) can i do it with SQL statement? and if yes are they different for different databases?
hamidreza_buddy wrote:
is there any difference between SQL statements we send to darabases or all of them support support a single tyoe of SQL statements
Yes and no. Most Structure Query Language statements are the same, but each database (MS SQL, MySQL, Oracle, Firebird, etc) have their own minor differences.
-
Hi as you know with OleDB we can open many kind of DataBases. i want to know is there any difference between SQL statements we send to darabases or all of them support support a single tyoe of SQL statements. I wanted to Get Information of tables of Databases(something like "Server Explorer" of VS.NET which opens every Type of Databases and shows their "Tables" and "Queries" and "procedures" and "Functions". abd also Field Types) can i do it with SQL statement? and if yes are they different for different databases?
Most support a industial standard called Sql-92 which will in theory work with any compliant SQL-92 database. But sadly in pratice it doesn't work like that and small quirks make problems porting sql code.
Look where you want to go not where you don't want to crash. Bikers Bible
-
Most support a industial standard called Sql-92 which will in theory work with any compliant SQL-92 database. But sadly in pratice it doesn't work like that and small quirks make problems porting sql code.
Look where you want to go not where you don't want to crash. Bikers Bible
Frank Kerrigan wrote:
Most support a industial standard called Sql-92
And some, like SQL Server 2005, now support SQL-99
Scottish Developers events: * .NET debugging, tracing and instrumentation by Duncan Edwards Jones and Code Coverage in .NET by Craig Murphy * Developer Day Scotland: are you interested in speaking or attending? My: Website | Blog
-
Frank Kerrigan wrote:
Most support a industial standard called Sql-92
And some, like SQL Server 2005, now support SQL-99
Scottish Developers events: * .NET debugging, tracing and instrumentation by Duncan Edwards Jones and Code Coverage in .NET by Craig Murphy * Developer Day Scotland: are you interested in speaking or attending? My: Website | Blog
I stand corrected :laugh:
Look where you want to go not where you don't want to crash. Bikers Bible
-
I stand corrected :laugh:
Look where you want to go not where you don't want to crash. Bikers Bible
You were correct in the fist place. You said "most" use SQL-92. I just thought I'd add that "some" now use SQL-99. If I remember correctly, SQL-92 is a subset of SQL-99, so it could be said that everything that is based on SQL-99 is, by default, also based on SQL-92.
Scottish Developers events: * .NET debugging, tracing and instrumentation by Duncan Edwards Jones and Code Coverage in .NET by Craig Murphy * Developer Day Scotland: are you interested in speaking or attending? My: Website | Blog
-
You were correct in the fist place. You said "most" use SQL-92. I just thought I'd add that "some" now use SQL-99. If I remember correctly, SQL-92 is a subset of SQL-99, so it could be said that everything that is based on SQL-99 is, by default, also based on SQL-92.
Scottish Developers events: * .NET debugging, tracing and instrumentation by Duncan Edwards Jones and Code Coverage in .NET by Craig Murphy * Developer Day Scotland: are you interested in speaking or attending? My: Website | Blog
I think SQL-92 relates to 1992 and SQL-99 relates to 1999. But I'm guessing
Look where you want to go not where you don't want to crash. Bikers Bible