Upsizing the Access Database into the SQL Server
-
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/dasanka/upsizingtheaccessdatabaseintothesqlserver.asp
My Blog:
http://dineshasanka.spaces.live.com/ -
I ran into a problem several years ago with the upsizing wizard. I don't remember the exact details but it had something to do with date/time fields. The problem was either caused by SQL Server having a more limited range of dates available in the datetime field that Access has in its equivalent or the Upsizing Wizard chose the smalldatetime when it should have picked the datetime data type. Regardless of the cause, the result was overflow-type errors when the wizard ran. So, if you run into errors like this, look at the data fields in the table that errors out and you'll probably find some data that won't fit into SQL Server for one of the above reasons.
[font="Tahoma"]Bryant E. Byrd, BSSE MCDBA MCAD[/font]
Business Intelligence Administrator
MSBI Administration Blog -
This article has useful information, but aren't there article editors at SQL Server Central that review articles before they are posted for public consumption? The grammar is this article is very stilted, and in some cases completely inaccurate, making it difficult to read. While I certainly don't fault the author for not being totally fluent in English, I do think it reflects badly on the quality of the site. Even a cursory read-through should have resulted in the vast majority of mistakes being fixed by an editor.
-
Have read about six articles on this over the years. The English in this article is weak, but a lot better than my Chinese. The writer has done a good job of summarising the issues and two available upsizing tools with lots of practical information. Thanks to him for writing it. It helps.
-
The one that I found in upgrading is that the Yes/No has to translate to the smallint (not bit) if you are front-ending with Access 97. It may have changed in Acc2K. But the values for boolean field are 0 and -1. The bit is 0 to 255 with no negatives.
----------------
Jim P.A little bit of this and a little byte of that can cause bloatware.
-
Kathi must have read my post before she wrote her article on the Access Upsizing Wizard
. She explains the problem I ran into and it looks like Access allows dates before 1753 and SQL Server does not. Kathi's article is at http://www.sqlservercentral.com/columnists/kKellenberger/accesstosqlservertheupsizingwizard.asp.[font="Tahoma"]Bryant E. Byrd, BSSE MCDBA MCAD[/font]
Business Intelligence Administrator
MSBI Administration Blog -
Very sorry for my porr english. I try to minize those in my next articles. Thank you very much for the comments. Its really helps me
My Blog:
http://dineshasanka.spaces.live.com/ -
No need to apologize, we all appreciate your effort and contribution to the community. I think Dave was a little harsher than he intended and his criticism was primarily aimed at our generous hosts. I think we need to step back and consider what has gone into building this community and give credit to our hosts for all the time and money they have put into this so that we can all benefit at no cost to us. I am sure that if some folks want to volunteer their time to do the proofreading the SQLServerCentral guys woud love the help.
Thanks Dinesh, keep the articles flowing!
[font="Tahoma"]Bryant E. Byrd, BSSE MCDBA MCAD[/font]
Business Intelligence Administrator
MSBI Administration Blog -
Thankx Tatsu
My Blog:
http://dineshasanka.spaces.live.com/ -
As I understand it, Access IS a RDBMS, but it is based on the JET engine rather than SQL and is only intended for a small number of users. Please correct your article, which states that Access is a "flat file" database.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply