I just got to thinking and realized I did not quite know the answer to this.
At what point does your data load start to outpace Access and should logically be moved to SQL Server? I know Access can handle millions of records and just has the limit of 2G per file, but at what point would you start losing performance due to the sheer amount of data? Or at what point should you start considering the transition due to size?
I have a database that is just used for warehousing. I use my companies report writer to do a data dump of all our sales on a daily basis and then upload that to this database and after just 3 months of use, I just surpassed 4 million records this morning which triggered this thought. This databases one and only purpose is to feed my Power BI reports. Should this be something I should consider moving to SQL Server to better manage per chance?
At what point does your data load start to outpace Access and should logically be moved to SQL Server? I know Access can handle millions of records and just has the limit of 2G per file, but at what point would you start losing performance due to the sheer amount of data? Or at what point should you start considering the transition due to size?
I have a database that is just used for warehousing. I use my companies report writer to do a data dump of all our sales on a daily basis and then upload that to this database and after just 3 months of use, I just surpassed 4 million records this morning which triggered this thought. This databases one and only purpose is to feed my Power BI reports. Should this be something I should consider moving to SQL Server to better manage per chance?