May 28, 2013 at 11:15 am
I have a split database that has one Back end and 3 front ends. Is it still possible to migrate over to SQL Server even though I have 3 different front ends accessing that one back end table?
May 28, 2013 at 11:34 am
Yes you can use same table for multiple applications, only thing you need to consider server performance (RAM, IO .....)
May 29, 2013 at 5:19 am
todd.ayers (5/28/2013)
I have a split database that has one Back end and 3 front ends. Is it still possible to migrate over to SQL Server even though I have 3 different front ends accessing that one back end table?
Your database being "split" is probably not the best description here.
A database and the data it holds is commonly accessed via multiple interfaces, including Sql Server Managment Studio and while there are certainly things to take into consideration when doing a migration the fact that multiple applications access the database in itself is not necessarily one of them.
May 29, 2013 at 8:20 am
I'd agree with OTC. You really have three applications that access the same back end. Split would imply you have parts of your database in one database and parts in another.
SQL Server excels at this. Arguably this site has 2 applications running against the same database.
May 29, 2013 at 8:30 am
So in migrating the back-end I would technically only be migrating one back-end with all 3 applications accessing it on the SQL server instead of the Access Db right?
May 29, 2013 at 8:54 am
Yes, though all the applications will have their connection strings change.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply