.NET migrate

[jas4th]

Hi,
I've got task of writing plan to migrate from Access databases to SQL Server 2000 and VB .NET. Apart from me nobody else has experience of VB .NET - just VBA (Access). They have gained some knowledge of SQL Server.
Can people give me ideas of things I need to think about and plan for in this migration, please?

Cheers.

[Carnifex]

I strongly recommend you research on MSDN the following classes.

(In the SqlClient Namespace)

SqlConnection
SqlTransaction
SqlDataReader
SqlCommand
SqlDataAdapter
SqlParameter

(In the System.Data Namespace)

DataSet
DataTable
DataView
DataRow
DataColumn

Also look at articles on DataBinding.

These are the main classes you are likely to use for your database interaction, have a read thru the descriptions of these classes and have a look at their members and you should get a thorough understanding of how databases work in ADO.Net

** Edit ** Just noticed you said access there will be similar classes in the OleDbClient namespace.

ADO.Net is completely different from ADO and you find that you are going to have recode large amounts of your database interaction.

[jas4th]

Thanks for this. To be honest I should have clarified - I have reasonable knowledge of .NET development (MCP trying for MCAD, MCSD - depends on your point of view as to whether this is of value - I think so but lets avoid flames).
What I need to produce is a plan, taking into account all the issues and risks that I can foresee, to take all internal systems over to SQL Server and .NET and the dev staff. I would like to take account and integrate OOP/D - or else I feel most of the point of the excercise will be missed.

[jwmoore2001]

I am not sure if you have the book by micrsoft in the MCSD self-paced training kit "Analyzing Requirements And Defining .NET Solution Architectures" but that is a great resource for just what you are trying to do.

In my opinion you will need to report to your supervisors the risks of continuing with the current systems outweigh the risks of bringing the system to a new platform or framework. This obviously is called Risk Management, which is a small part of analyzing the business needs. Really you will have many tasks at hand in converting and/or convincing higher authority to move to a new technology. Present case and point in as much detail as you can, Excel and word files outlining ideas and ROI forecasts, etc.

In case you dont already know SQL Server 2000 has data transformation services to help migrate data from another source.

I hope I understood your question properly, if not please let me know.

[jas4th]

Thanks. I had been starting to consider these books for MCSD exam. I've heard recommendations for "MCSD .NET Solution Architectures Exam Cram 2" from QUE - does anyone have any opinions about this one please?

[jwmoore2001]

I am not sure about the exam cram book, but I can tell you I have the Microsoft Press MCAD/MCSD Self-Paced Training Kit that includes 4/5 required areas in four seperate books for the MCSD requirements. These are excellent books. The book I explained earlier for the required exam 70-300 Anaylizing Requirements And Defining .NET Solution Architecture is an absolutely imparitive book to have when studying for that test. It explains everything in great detail and includes all the sample Excel and Word Templates.

I will probably get an exam cram book before taking some of the other tests to ensure I am ready.

[microfast]

Hiya,
I am busy upgrading from VB5 to .Net, and from Access '97 to SQL 2000.
Here's my plan so far:
1. Upgrade VB5, to connect to Access, from using DAO to ADO first.
2. Upgrade to VB6 (I have the learning edition) from VB5 using the ActiveX upgrade Wizard.
3. Import to VB.Net (still using ADO to MS Access, OLE).
4. Upgrade the database from Access to SQL, including changing queries to Stored Procedures.
5. Upgrade VB.Net to use SQL Client, includes upgrade Access Views to SQL Stored Procedures, and Access Reports to Crystal Reports !

Pheeewww !! What a job !

[nswan]

if you are upgrading DAO to ADO, why not miss out ADO and go straight to ADO.NET?

(you might have meant that but just thought i'd ask)

[microfast]

Hi.
There is too much code to be changed, e.g. 150 occurences of the word "recordset". It is easier first to get the bulk of the code done in VB5 first, and then go to 6 and then .Net.
Also, Microsoft recommend using the VB6 "Upgrade ActiveX Wizard" before going to .Net