250 likes | 359 Views
GTS DB Conversion. Going from MS Access to MS SQL Server can be simple… if you let it be. What we did…. Used MS Access 2007 Fixed VB Issues with Access 2007+ Copied Structures and Data up to the Server Added a couple of Indexes on frequently used fields Setup User Security.
E N D
GTS DB Conversion Going from MS Access to MS SQL Server can be simple… if you let it be.
What we did… • Used MS Access 2007 • Fixed VB Issues with Access 2007+ • Copied Structures and Data up to the Server • Added a couple of Indexes on frequently used fields • Setup User Security
Hurdles we faced… • Leaving design open for a more Optimal UI to be designed • Change the way Users think about “searching” through their data • Change control?
Why MS Access 2007? Reasons…: • The Wizard makes it easy, especially compared to prior versions of MS Access. • The Wizard makes it easy. • Seriously… you need another reason?
Why not MS Access 2007? There are reasons not to use the Wizard… or to use it differently. • You can design from the Ground up… then push data(i.e.: No more complaints about prior developers). • You can just push the structures, then tweak it.(Useful for particularly large sets of data and data file management)
VB Issues with Access 2007 It could happen to you…
VB Issues with Access 2007 Luckily for us, it’s easy to fix.
Copy Structures and Data to the Server “…if ever a Wiz there was! ...”
Added a couple of Indexes CREATE NONCLUSTERED INDEX [PI_LName] ON [dbo].[tblPI] ( [PI] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF…