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 |
|
dmoonme
Starting Member
13 Posts |
 Posted - 2006-10-30 : 13:27:57
|
| Hello and thanks for your help in advance.So what I need to do is store applications info, such as application name, path, server it's installed on, etc., into a table. I thinking of designing the table like this but not sure if this is a good design:ApplicationInfo---------------ID Application -- pkPathServerNameThere are apps that are installed on all servers and there are some apps installed only on a few servers. I was thinking of making the "Application" field unique so that only 1 instance of the application name exists and then comma delimit the "ServerName" field values.So with this approach records would look like this:Field Value-----------------------------------ID "1"Application "Adobe"Path "C:\Program Files\Adobe"Server "ServerA,ServerB,ServerC"ID "2"Application "Microsoft Office"Path "C:\Program Files\Microsoft Office"Server "ServerB,ServerC"What would you recommend doing? |
|
|
X002548
Not Just a Number
15586 Posts |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2006-10-30 : 15:33:07
|
quote:
Originally posted by dmoonme...I was thinking of making the "Application" field unique so that only 1 instance of the application name exists and then comma delimit the "ServerName" field values...
Since your table would not even be in first normal form, I would have to say it is a very bad design.Think about how you would write a query to see all the applications installed on each server to see haw bad it would be.CODO ERGO SUM |
 |
|
|
dmoonme
Starting Member
13 Posts |
Posted - 2006-10-31 : 16:45:32
|
| Thanks for the replies. I figured my design was not a good one. |
|
|
|
|
|
|
Suggestions on design of table