Intended audience: Application developers who are not familiar with designing, implementing or maintaining databases, yet need to create a database for use with their applications.
The links below are external links and provide information and guidance on understanding how to design, create and maintain databases using SQL Server, as well as avoiding common mistakes during database design.
A well thought out database design will reduce data storage requirements by normalizing data, increase performance through organization and indexing of data, and will generally help you avoid revisiting and redesigning your database multiple times during
application development. Ten Common Database Design Mistakes provides a list of ten of the more common design mistakes, as well as the consequences of
these mistakes. The other links in this section provide additional resources to help you successfully design the database(s) used by your application.
T-SQL is the query language used to communicate with, and act upon, the data contained within a SQL Server database. While there are other ways to interact with this data from within an application, such as LINQ, for most interactions with the database you
will be required to use T-SQL.
A data-tier application (DAC) is an entity that contains all of the database and instance objects used by an application. A DAC provides a single unit for authoring, deploying, and managing the data-tier objects instead of having to manage them separately.
This article is also available in the following languages:
Thanks for this wiki.
I wrote a post on elmozamil.blogspot.com about store procedure to make my application in layers, I mean if I have stored procedure for my logic, and application, and tables, views. isn't make my application more manageable and adaptable for changes.
I hope get an answer.
Thanks for such a nice wiki