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 |
|
iwaters
Starting Member
13 Posts |
 Posted - 2003-02-11 : 08:57:48
|
| I need to create a database which will store monthly figures for various Performance Indicators. Easy enough, however the data will run form April-to-April i.e. the Financial Year. How should I store this infoformation so I know which year the data refers to? I will also need to be able to create the web based front end to the app, which will need to know when the data starts from etc. To make it even harder some of the indicators will stop being used at the end of the year and other will continue to the next year. Any ideas for the design of the tables? |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2003-02-11 : 12:51:12
|
| why not have a 'reporting-period' table...with the following structure....period (code,name, start, end)....(i know, i know...that it is not necessary to have a 'code' column....but it's what i'm comfortable with)and data....1, FinYear#1, 1/4/2003, 31/03/20042, finyear#2, 1/4/2004, 31/03/20053, finyear#1-qtr1, 1/4/2003, 30/06/20034, finyear#1-qtr2, 1/7/2003, 30/09/2003etc....and then join this table to your main table with the dates.re indicators....my advice...build them all in as if they are going to be used forever....and then just get the code to make them 'null/0/whatever' when no longer required.and diary yourself for 2 years time to drop the columns when the entire column contains 'null/0/whatever' |
 |
|
|
|
|
|
|
|
Database for Tax/Financial Year