asp.net 4.0和后端，SQL Server 2008中的项目 [英] project in asp.net 4.0 and in back end, sql server 2008

问题描述

大家好

我想在asp.net 4.0中做一个项目，而在后端，sql server 2008是我的选择...
在数据库的情况下我应该考虑什么...
我的意思是在安装，命名实例，sql配置，nt权限网络服务等情况下....


有什么可以帮助我的，您的宝贵建议...

在此先感谢

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

推荐答案

安装:让客户自行解决.不要尝试为客户或自动安装SQL Server.
有两个原因:
0)您只能出于版权原因分发SQL Server Express-不能分发SQL Server完整版.
1)他们可能已经在网络上安装了SQL Server.如果是这样，那么他们大概会想使用该版本.
2)如果他们确实安装了SQL Server，并且您开始激增SQL Server Express实例，那么您将烦恼数据库管理员...
3)与在用户控制下的多个分散版本相比，备份SQl Server的单个站点的可能性要大得多.
4)对于普通"用户来说，安装和管理Sql Server非常复杂-这不是一个好主意！
5)它将破坏使用SqlServer而不是SqlCE或SQLite的主要优势-多用户访问.如果每个人都安装了自己的SQL Server副本，那么您将拥有数据库的多个副本，每个副本都由一个人使用.这将引起一些混乱，并且(取决于您编写原始数据库的方式)在实现问题时可能需要花费相当大的精力才能组合成一个实例.
命名实例:请参见上文
实际上，对于不确定的所有功能，请参见上文！

为了进行开发，请在计算机上安装SQL Server或SQL Server Express，然后使用本地实例.将所有连接详细信息保存在配置文件中，以便在投入生产时可以轻松更改它，而无需重新编译代码.

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.

这篇关于asp.net 4.0和后端，SQL Server 2008中的项目的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！