jonathanchye
Registered User.
- Local time
- Today, 12:52
- Joined
- Mar 8, 2011
- Messages
- 448
Due to recent changes in the company I'm required to convert/migrate the backends of my MS Access 2010 databases to SQL.
I've experimented with using the built in tool but seem to have some problems with some of my forms and queries. I guess it would be the stricter restrictions of SQL servers vs MS Access.
I currently do have a basic SQL server connection to manage user pings. Basically a simple code which checks every few seconds to see if the user is still logged on and updates a table on a SQL Express Server. Very basic stuff but seems to have been working well.
My implementation plan is to host the SQL using Hyper-V running Windows Server 2012 and SQL 2012 R2. I'd have to consult with our IT vendor and also find out the costs but from research this seems to be the ideal solution. What RAM would be the recommended minimum?
I am hoping that someone who have done something like this before can kindly provide some tips and pointers or perhaps provide any links/sources of helpful information.
Thank you!
I've experimented with using the built in tool but seem to have some problems with some of my forms and queries. I guess it would be the stricter restrictions of SQL servers vs MS Access.
I currently do have a basic SQL server connection to manage user pings. Basically a simple code which checks every few seconds to see if the user is still logged on and updates a table on a SQL Express Server. Very basic stuff but seems to have been working well.
My implementation plan is to host the SQL using Hyper-V running Windows Server 2012 and SQL 2012 R2. I'd have to consult with our IT vendor and also find out the costs but from research this seems to be the ideal solution. What RAM would be the recommended minimum?
I am hoping that someone who have done something like this before can kindly provide some tips and pointers or perhaps provide any links/sources of helpful information.
Thank you!