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 |
|
indersshekhawat
Starting Member
26 Posts |
 Posted - 2008-03-25 : 02:02:34
|
| I have two issue first is <----------------------------------------->in my database 2 tables are mostly uses. Name as -> 1. LotMaster 2. Process LotMaster is primary tables and process is secondary ut process tables have many column which are already in LotMaster should i remove all the duplicate column. after removing i can my work with joinsecond issue is <-----------------------------------------------> some column are already in database which have no data(always null) and not necessary for me is that column effect my database speed.(i want to remove that database) |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-25 : 03:23:28
|
| 1. Depends if you want it denormalized for performance reasons. But as a starter, normalize the database properly by keeping only the key columns in the child tables.2. It does not affect your speed, just affects storage. But it would be a good idea to remove them since they aren't in use.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
indersshekhawat
Starting Member
26 Posts |
Posted - 2008-03-25 : 03:51:45
|
| i think removing column will reduse my network trafic ?any idea? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-25 : 12:13:07
|
| Not if you are explicitly specifying which columns to return to your application.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
Should i remove duplicate column