>Hi to all.
>I need to design a Database that incorporates an Accounts Module. In VFP database I was using seperate folders to hold database of each new Financial Year. I could change the folder uning CD command and use the same table names in the programs.
>
>I think seperate storage will make the operation and backups faster as during operations the database is loaded into RAM in the form of pages.
>
>How can Financial Years be handled in SQL Server? Should all the data spanning different Financial years be kept in one big Database or is it possible to keep it seperately?
>
>Please advise.
>
>Thank in advance.

Aman,

As previously mentioned, there is not a compelling reason to break up fiscal years into separate databases or tables on SQL Server.

I want to add that a good database design for financial data will also include a "cut-off" number of years into the past where before the cut-off, only aggregated data is kept "online".

This will help with historical reports. These kinds of queries are the ones that typically take 30 minutes or more to run.