Database Design Microsoft SQL Server

Was thinking of creating a small application in c# but would like to hear some feedback on approaching my project with this method.

Basically I will have 2 tables in MSSQL

    These are just examples....



So when a user wants to create a new table say birds the value would go into the tabletype create an autoid and then have the Type as birds. The name for the bird, Color, size would go into the TableInfo Table.

  • Calling a stored procedure from CodeIgniter's Active Record class
  • What is corresponding c++ data type to SQL numeric(18,0) data type?
  • How do I split two columns in two separate tables into joined multiple rows in a view?
  • SQL Server: Importing and archiving weekly data
  • optimized way to get row count from a query contains large amount of data
  • Get child records of selected rows from database
  • But now lets say that they would like to create a new table called auto. So again auto would go into tabletype under the type column and then the auto’s color, size, tagnumber would all go into the next table.

    Is this the right way to approach this or will this cause a lot of issues with programming in the future


  • What is the difference between primary, unique and foreign key constraints, and indexes?
  • mssql giving logins(users) db_owner access to database
  • Why is “close existing connections to destination database” is grayed out on SQL Server 2012 Management Studio?
  • Insert 2 million rows into SQL Server quickly
  • 50894 ERROR reading: Incorrect syntax near the keyword 'user' when tries to select query to compare the username and password
  • Subquery returns more than 1 value SQL error on multiple selection
  • 2 Solutions collect form web for “Database Design Microsoft SQL Server”

    This is a weird misuse of Table Inheritance, and it’s not a good idea.

    If you want to store info about birds in a relational database, you should have a table called Bird(s) that stores info only about birds. And have a different one for Autos.

    You could consider using table inheritance for related types, such as Tits and Swallows

    Yes, this could be one way of doing based on the information you have provided.

    I am guessing you will have different table types added overtime, may be even dynamically, and your code will map to a different object type on the business logic side based on those table types.

    your names are confusing though, instead of using TableType, perhaps a better name could be RecordType and RecordDetails or RecordInfo.

    MS SQL Server is a Microsoft SQL Database product, include sql server standard, sql server management studio, sql server express and so on.