>
>Hi Gregory,
>
>For me using just one database sounds like a good approach. I remember I was having a similar problem in 2003 when I needed to create a SQL Server database for something we had in FoxPro. We had databases for each state (MA, RI, CT, NH) and I was thinking of creating a SQL Server database for each state as well. Luckily I called Sergey that time and he helped me to figure out that SQL Server is a completely different storage and you don't need to worry about 2GB limit, etc.


I do believe that for your problem ONE database was better than many