project in asp.net 4.0 and in back end, sql server 2008

Question

0.00/5 (No votes)

See more:

hi all

i want to do a project in asp.net 4.0 and in back end, sql server 2008 is my option ...
what thing i should i consider in the case of database...
i mean in the case of installation,named instance, sql configuration.nt authority network service etc....

Can any help me with your valuable advice...

thanks in advance

Posted 1-Dec-11 21:18pm

Ragi Gopi

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2011-12-01T21:37:00

Installation: Let the customer take care of it. Do not attempt to install SQL Server for the customer, or automatically.
There are a couple of reasons:
0) You can only distribute SQL Server Express for copyright reasons - not SQL Server full version.
1) They may already have SQL Server installed on the network. If so, then they will presumably want to use that version.
2) If they do have SQL server installed and you start proliferating SQL server Express instances, you are going to annoy the heck out of the database administrator...
3) A single site installation of SQl Server is a lot more likely to be backed up than a number of scattered version under user control.
4) Sql server is quite complex for a "normal" user to install and administer - it is not a good idea!
5) It will destroy the primary advantage of using Sql Server over SqlCE or SQLite - multiuser access. If everyone installs their own copy of SQL server, then you will have multiple copies of your database, each used by a single person. This will cause some confusion, and (depending on how you wrote the original database) may take some considerable effort to combine into a single instance when the problem is realized.
Named Instance: See above
In fact, see above for all of the features you are unsure of!

For development, install SQL server or SQL server Express on your machine, and use the local instance. Keep all connection details in a configuration file so that it can be easily changed when it goes to production, without re-compiling your code.