RE: Database development

From: Bonj (Bonj_at_discussions.microsoft.com)
Date: 11/12/04


Date: Fri, 12 Nov 2004 03:19:01 -0800

You don't really write a database "in C#".
Do you mean you want to write a database *backend* in C#, or you want to
write an application that *uses* a database (running on an existing backend)
in C#?
If the former, then it's no small task, and it'd probably be fairly poor if
it didn't use at least a bit of C/C++. If the latter, then SQL Server (free
versions are MSDE 2000 or SQL Server Express 2005 Yukon) is the best bet as
it includes support for stored procedures which enable you to isolate a layer
of processing to the backend, black-box-ed off to your C# app. Watch out for
Yukon's dodgy new provider though - it doesn't seem to use the standard
OLEDB, instead going for something called "SQL native client". I had a little
dabble with it but it put me off as I had a project to do quickly, but I
might spend further time investigating when I've got the time.
Basically though, C# includes the System.Data.SqlClient namespace which
contains objects for accessing SQL server databases directly without using
OLEDB, hence is probably the fastest way of doing it.

"Hemang Shah" wrote:

> Hello I"m a seasonal Access developer.
>
> How steep is the learning curve to start developing database applications
> in c# ?
>
> Could you suggest me any good books which teaches the ropes of
>
> database development in C# ? Including making reports ?
>
>
>
> Thanks
>
>
>
>
>



Relevant Pages

  • Re: Replication Suggestions
    ... Looking for a SQL Server replication book? ... >I have an application with a sql backend. ... > database on the webbox and an internal database for inter-company use. ...
    (microsoft.public.sqlserver.replication)
  • Re: Help with SQL statement
    ... SQL Server, all of the processing is done on the server, with Access ... case with ADO when using an Access backend. ... new table in the backend instead of in my local database. ... I will use the append query version. ...
    (microsoft.public.access.reports)
  • Re: splitting database
    ... regrding use of sql server as backend. ... With best regards, ... bibliographic database for a library. ...
    (microsoft.public.access.modulesdaovba)
  • Re: splitting database
    ... as you have such a big tables - I think best option is to use SQL Server as backend, you will have one set of tables and that is ... bibliographic database for a library. ... Whether its better to use sql server as backend datbase. ... > For linking multiple databases what should I do? ...
    (microsoft.public.access.modulesdaovba)
  • RE: One backend across multiple sites
    ... If your backend database is SQL Server then it can be done. ... We have servers at each remote site and they are updated via DFS. ...
    (microsoft.public.access.tablesdbdesign)