• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 227
  • Last Modified:

SQL Database Design Best Practice

Hi, I'm designing a database for a project and need to make it as versatile as possible as there may be many changes to the data structure stored in future. I've decided to use name/value pairs for storing parameters instead of extra columns. e.g.:

Tables:
Reports
ReportDetails

Columns:
Reports.ID, Reports.Name, Reports.Desc etc
ReportDetails.ID, ReportDetails.ReportID, ReportDetails.ParameterName, ReportDetails.ParameterValue

This structure enables the storing of any new report type including its new parameters without changing the DB structure.

Is there a downside to this approach?
0
DamoD0
Asked:
DamoD0
1 Solution
 
BawerCommented:
i personally recommend that its not required to put many columns in a single table, the structure you have created for two table is fare enough, and there will be no downside so far
0
 
DamoD0Author Commented:
Thanks, makes sense.
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now