|
|
Posted by Beowulf on 11/28/06 20:52
Ted wrote:
> Hi Sam,
>
> My first question is this: "If you were in my place, and wanted to
> simplify deployment, would you use some of the ADO.NET classes to copy
> the MS Access database to SQL Server, and then deploy SQL Server 2005
> Express with your application, or use the Jet engine for both the
> existing Access database and the new recipe database, or leave the
> Access database as it is and create a SQL Server Express database for
> the new database?"
Yes, I would have utilities or procedures that could read data in
various formats, but would store and deploy all my data in one standard
database format(such as SQL Server 2005 Express), if possible, to
simplify application development and maintenance.
> A second question is this: "Is the dialect of SQL used by Access the
> same as that used by SQL Server 2005?"
No, not by a long shot. Different built-in functions (such as IIF() and
CStr() in Access vs CASE statement and CAST() in SQL Server), different
wild cards (* in Access vs % in SQL Server - and completely different
regular expressions for the LIKE statement), different data types, etc.
Some overviews of the differences:
http://sqlserver2000.databases.aspfaq.com/what-are-the-main-differences-between-access-and-sql-server.html
http://www.mssqlcity.com/Articles/Compare/sql_server_vs_access.htm
Navigation:
[Reply to this message]
|