Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

SQL / .NET Framework Question

Posted on 2007-03-27
6
208 Views
Last Modified: 2013-12-17
I want to use a SQL database for an application I'm writing.  It was using an Access database, but the database will eventually collapse (a fairly long time from now) because the size will eventually be too large for an Access database.   So, we want to move over to SQL before that happens.  Originally, the usage was that there was a database of x-rays with all the identifying information.  The software just read out of that database to open selected x-rays.  We just want to make that Access database into a SQL database.  However, I've never used SQL before.  I started writing code in MSVS C# 2005 Pro edition using the .NET Framework and the System.Data.Sql namespace.  Now, if I write code with that, will each client computer now have to have an SQL Server on their system?  The application will be the only thing accessing that database and it'll never be accessed over the network.

So, the main question is, "will an installation of a SQL server be absolutely required on each client system with the application?"  If I do need a SQL Server installed on each machine, would I be allowed to install MS Sql Server 2005 Express edition on each machine or would that be against the licensing (i never understand EULAs)?

A secondary question is just asking if anybody knows of any good references for using the System.Data.Sql namespace to write a project and also any good references for anything else related to SQL that I should know.
0
Comment
Question by:raw_enha
  • 3
  • 2
6 Comments
 
LVL 16

Expert Comment

by:rboyd56
ID: 18800091
SQL Server does not need to be installed on each system. You can have each client machine access a remote SQL Server which will store the data in a central location.

However, if the clients will be disconnected at times from the network or if they need to make updates to a separate database than the central server then it might be best to install SQL Server Express on the client machines.

It really depends on the architecture of the application.

But as a general rule all clients can access the same SQL Server as the backend of the application.
0
 

Author Comment

by:raw_enha
ID: 18800223
We don't want everyone to access it centrally.  We want them all to have their own SQL DB on their computer.  Not all of them have internet access.  This is for an application that gets sold to the user.  We needed something better than an Access database though.
0
 
LVL 16

Expert Comment

by:rboyd56
ID: 18800284
Then yes you will need to install SQL Server on each client. SQL Server Express will work for this. It is basically what it is designed for.
0
Master Your Team's Linux and Cloud Stack!

The average business loses $13.5M per year to ineffective training (per 1,000 employees). Keep ahead of the competition and combine in-person quality with online cost and flexibility by training with Linux Academy.

 

Author Comment

by:raw_enha
ID: 18801213
We build the computers before hand for the customer.  So, it will be legal for us to install SQL Server 2005 Express on there before giving them the computer?
0
 
LVL 16

Accepted Solution

by:
rboyd56 earned 500 total points
ID: 18801522
If you are shipping an application that uses SQL Server Express on it I would assume so. SQL Server Express is freely distributable with an application developed in Visual Studio 2005 that uses SQL Server Express.
0
 

Expert Comment

by:climberboy
ID: 18803418
rboyd56 is correct.  Use the Express Version, and make it a dependancy in your application setup project.  It will install automatically when the user installs your application.

For ADO.Net / SQL, use enterprise library.  It's very well thought-out, and you can get a grip on how it works without too much effort.

If you need, email me at eric@pixelninjas.com and I will send you some sample N-Tier code to manage your DAL, BLL, and Front end.

Thanks,

Eric.
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In SQL Server, when rows are selected from a table, does it retrieve data in the order in which it is inserted?  Many believe this is the case. Let us try to examine for ourselves with an example. To get started, use the following script, wh…
Data architecture is an important aspect in Software as a Service (SaaS) delivery model. This article is a study on the database of a single-tenant application that could be extended to support multiple tenants. The application is web-based develope…
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question