<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server 2008 - General
»
things to know when designing a new database
15 posts, Page 1 of 2
1
2
»»
things to know when designing a new database
Rate Topic
Display Mode
Topic Options
Author
Message
DBA24
DBA24
Posted Monday, January 21, 2013 2:52 PM
SSC Rookie
Group: General Forum Members
Last Login: Wednesday, March 06, 2013 7:44 AM
Points: 25,
Visits: 26
what are things one need to always keep in mind when designing a new database for an application
Post #1409723
GilaMonster
GilaMonster
Posted Monday, January 21, 2013 3:10 PM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 4:49 PM
Points: 37,722,
Visits: 29,977
Maybe start with this:
http://www.amazon.com/Server-Relational-Database-Implementation-Experts/dp/143020866X/
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass
Post #1409726
ScottPletcher
ScottPletcher
Posted Monday, January 21, 2013 3:13 PM
Ten Centuries
Group: General Forum Members
Last Login: Today @ 3:56 PM
Points: 1,324,
Visits: 1,778
What you really need is someone that has experience doing it, period. This is
not
something that you can just "wing it".
If you have to do it with no experience, just expect up front that you'll have to re-do things, sometimes the same thing multiple times.
The next most important thing is to separate the logical and physical design phases -- do
NOT
allow
anyone
to skip the logical phase and immediately start designing "tables" or "indexes".
SQL DBA,SQL Server MVP('07, '08, '09)
One man with courage makes a majority. Andrew Jackson
Post #1409728
DiverKas
DiverKas
Posted Tuesday, January 22, 2013 10:57 AM
SSC Veteran
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 10:24 AM
Points: 237,
Visits: 413
1) Do NOT let your C#/VB/ASP/Pascal guys design the database.
2) Do NOT let your DBA's design the database.
3) Hire a Data Architect.
Just saying. The first 2 groups have very biased views of how data should be structured for VERY different reasons, neither of which usually solves the entire problem.
Post #1410167
ScottPletcher
ScottPletcher
Posted Tuesday, January 22, 2013 11:15 AM
Ten Centuries
Group: General Forum Members
Last Login: Today @ 3:56 PM
Points: 1,324,
Visits: 1,778
DiverKas (1/22/2013)
1) Do NOT let your C#/VB/ASP/Pascal guys design the database.
2) Do NOT let your DBA's design the database.
3) Hire a Data Architect.
Just saying. The first 2 groups have very biased views of how data should be structured for VERY different reasons, neither of which usually solves the entire problem.
#2 is NOT necessarily true -- it depends on the DBA. I have long-term experience in all phases of the design process.
Also, if you hire someone who's solely a Data Architect, then you have to hire an
additional
person to convert the logical model into a physical model.
SQL DBA,SQL Server MVP('07, '08, '09)
One man with courage makes a majority. Andrew Jackson
Post #1410183
prathibha_aviator
prathibha_aviator
Posted Tuesday, January 22, 2013 11:23 AM
SSC Journeyman
Group: General Forum Members
Last Login: Yesterday @ 9:12 AM
Points: 95,
Visits: 223
I believe u should also have thorough understanding on relationships and length, size of the variables. They cost u a lot when it comes to the performance.
--Pra
--------------------------------------------------------------------------------
Post #1410187
Sean Lange
Sean Lange
Posted Tuesday, January 22, 2013 1:13 PM
SSCrazy Eights
Group: General Forum Members
Last Login: Today @ 2:52 PM
Points: 8,605,
Visits: 8,246
ScottPletcher (1/22/2013)
DiverKas (1/22/2013)
1) Do NOT let your C#/VB/ASP/Pascal guys design the database.
2) Do NOT let your DBA's design the database.
3) Hire a Data Architect.
Just saying. The first 2 groups have very biased views of how data should be structured for VERY different reasons, neither of which usually solves the entire problem.
#2 is NOT necessarily true -- it depends on the DBA. I have long-term experience in all phases of the design process.
Also, if you hire someone who's solely a Data Architect, then you have to hire an
additional
person to convert the logical model into a physical model.
Neither is #1. There is no rule that says a developer is unable to design a proper database because they are a developer.
_______________________________________________________________
Need help? Help us help you.
Read the article at
http://www.sqlservercentral.com/articles/Best+Practices/61537/
for best practices on asking questions.
Need to split a string? Try Jeff Moden's
splitter
.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs
Post #1410242
GilaMonster
GilaMonster
Posted Tuesday, January 22, 2013 1:25 PM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 4:49 PM
Points: 37,722,
Visits: 29,977
Sean Lange (1/22/2013)
ScottPletcher (1/22/2013)
DiverKas (1/22/2013)
1) Do NOT let your C#/VB/ASP/Pascal guys design the database.
2) Do NOT let your DBA's design the database.
3) Hire a Data Architect.
Just saying. The first 2 groups have very biased views of how data should be structured for VERY different reasons, neither of which usually solves the entire problem.
#2 is NOT necessarily true -- it depends on the DBA. I have long-term experience in all phases of the design process.
Also, if you hire someone who's solely a Data Architect, then you have to hire an
additional
person to convert the logical model into a physical model.
Neither is #1. There is no rule that says a developer is unable to design a proper database because they are a developer.
I'm a developer (SQL mostly, not front end). I'd argue that I can design at least a passably good database.
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass
Post #1410246
Sean Lange
Sean Lange
Posted Tuesday, January 22, 2013 2:15 PM
SSCrazy Eights
Group: General Forum Members
Last Login: Today @ 2:52 PM
Points: 8,605,
Visits: 8,246
GilaMonster (1/22/2013)
Sean Lange (1/22/2013)
ScottPletcher (1/22/2013)
DiverKas (1/22/2013)
1) Do NOT let your C#/VB/ASP/Pascal guys design the database.
2) Do NOT let your DBA's design the database.
3) Hire a Data Architect.
Just saying. The first 2 groups have very biased views of how data should be structured for VERY different reasons, neither of which usually solves the entire problem.
#2 is NOT necessarily true -- it depends on the DBA. I have long-term experience in all phases of the design process.
Also, if you hire someone who's solely a Data Architect, then you have to hire an
additional
person to convert the logical model into a physical model.
Neither is #1. There is no rule that says a developer is unable to design a proper database because they are a developer.
I'm a developer (SQL mostly, not front end). I'd argue that I can design at least a passably good database.
Gail we are saying the same thing. I think anytime someone starts segregating abilities based on job title they are destined to get snowballed. I too am a developer and would like to think I could cobble something usable together.
_______________________________________________________________
Need help? Help us help you.
Read the article at
http://www.sqlservercentral.com/articles/Best+Practices/61537/
for best practices on asking questions.
Need to split a string? Try Jeff Moden's
splitter
.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs
Post #1410265
ScottPletcher
ScottPletcher
Posted Tuesday, January 22, 2013 3:20 PM
Ten Centuries
Group: General Forum Members
Last Login: Today @ 3:56 PM
Points: 1,324,
Visits: 1,778
Sean Lange (1/22/2013)
GilaMonster (1/22/2013)
Sean Lange (1/22/2013)
ScottPletcher (1/22/2013)
DiverKas (1/22/2013)
1) Do NOT let your C#/VB/ASP/Pascal guys design the database.
2) Do NOT let your DBA's design the database.
3) Hire a Data Architect.
Just saying. The first 2 groups have very biased views of how data should be structured for VERY different reasons, neither of which usually solves the entire problem.
#2 is NOT necessarily true -- it depends on the DBA. I have long-term experience in all phases of the design process.
Also, if you hire someone who's solely a Data Architect, then you have to hire an
additional
person to convert the logical model into a physical model.
Neither is #1. There is no rule that says a developer is unable to design a proper database because they are a developer.
I'm a developer (SQL mostly, not front end). I'd argue that I can design at least a passably good database.
Gail we are saying the same thing. I think anytime someone starts segregating abilities based on job title they are destined to get snowballed. I too am a developer and would like to think I could cobble something usable together.
Perhaps. But I would not want someone who had not been a full-time database designer or DBA at some point to head a db design. Based on my past experiences, (almost) pure developers can't seem to forget
physical
details long enough to do a proper
logical
design. Any who could do it properly would be the rare exceptions, not the normal rule.
SQL DBA,SQL Server MVP('07, '08, '09)
One man with courage makes a majority. Andrew Jackson
Post #1410279
« Prev Topic
|
Next Topic »
15 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
