Home Forums Database Design Design Ideas and Questions Avoiding Large Number of db Columns in SQL Server - Database Redesign RE: Avoiding Large Number of db Columns in SQL Server - Database Redesign

  • December 4, 2013 at 2:23 pm

    #1670854

    LutzM (11/27/2013)

    I'd go with a separate table with the columns ObjectiveId (as a foreign key reference to the current table), OutcomeId, KSA_aspectNo, KSA_AspectValue together with a column referencing the related.

    I'm not sure if I'd go for a separate Identity column as the clustered index or if I'd use ObjectiveId, OutcomeId, and KSA_aspectNo as the natural key.

    Most probably I'd go with the separate column together with a few constraints... It depends 😉

    Thanks! That helps alot.

    When doing inserts into these tables from my Classic ASP Application, I had thought of inserting the PK in the form of a GUID generated by the application. My challenge was 'how to insert it for use in each table simultaneously?'

    Is there a problem with doing it this way, or would using an Autonumber with some sort of trigger to the other tables be possible/preferrable?

    Thanks again for any input. 🙂