Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
rajani
Constraint Violating Yak Guru
367 Posts |
Posted - 2005-10-31 : 21:02:18
|
| Hi friendsI've quick question with database design.we are designing database for our new app.we've some common fields that will be there almost every table.they areupdated by ,updatedDt and their datatypes int,datetime respectively.my question is is it good design to have user defined data types for these common columns.i mean we create UD datatype with above system datatypes and we assign thsese when we create above fields.is it good design approach?any disadvantages ?Cheers |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-10-31 : 21:11:38
|
| It is good. The disadvantage would be if you tried to implement UDTs without defining your standards first. If you do this, they will be a disaster. Other then that, UDT's are a great way to help facilitate standardized design across an enterprise. This is my 2 cents. We'll see what others say.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
rajani
Constraint Violating Yak Guru
367 Posts |
Posted - 2005-10-31 : 21:48:45
|
| Thanks derrickThats what i wanted hearCheers |
 |
|
|
byrmol
Shed Building SQL Farmer
1591 Posts |
Posted - 2005-11-01 : 00:44:32
|
| >>Thats what i wanted hearI can't let that stand...UDT's suck! They will make you sterile.Now that you have both sides of the story I will let you decide... :-)DavidMA front-end is something that tries to violate a back-end. |
 |
|
|
spirit1
Cybernetic Yak Master
11752 Posts |
Posted - 2005-11-01 : 06:35:03
|
we use them, i dislike them for no particular reason ... Go with the flow & have fun! Else fight the flow |
 |
|
|
|
|
|