Wrox Programmer Forums
|
SQL Server 2000 General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old June 6th, 2003, 10:26 AM
Authorized User
 
Join Date: Jun 2003
Posts: 98
Thanks: 0
Thanked 0 Times in 0 Posts
Default RE: Upsizing wizard

Hello,

I am trying to test one of the DB at work by upsizing it to SQL. I have a problem with upsizing the wizard in Access. I receive the message Overflow and I went to google.com and it said to download Access 2000 and SQL Server 2000 Readiness Update and when I do it gives me an error that says it is not in SR-1 level. I then kept searching for other solutions and another website explained that before installing Access 2000 and SQL Server 2000 Readiness Update to install Microsoft Office 2000 SR-1 and when I do it is saying that my network resource is unavailable. Any suggestions? Your help is greatly appreciated.

Thank you

slypunk
__________________
slypunk
 
Old June 10th, 2003, 12:50 PM
Authorized User
 
Join Date: Jun 2003
Posts: 34
Thanks: 0
Thanked 0 Times in 0 Posts
Default

All the upsizing wizard does really is upload the tables in your access db. If your having trouble with the wizard then just try it the other way around; create a new db in your server, then just import your access tables either through an import wizard or a DTS.

Thanks,
Jesse
 
Old June 12th, 2003, 12:19 PM
Registered User
 
Join Date: Jun 2003
Posts: 8
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hi

I've recently been moving Access MDBs into SQL 2k and hit the same error.

Turned out that SQL DTS was creating Access Date/Times as SmallDateTimes. In the end the only way I could fix this was to manually amend the tables in DTS then wrote a simple script to change all small dates to date times.

Regards
Graham
 
Old June 12th, 2003, 12:49 PM
Authorized User
 
Join Date: Jun 2003
Posts: 41
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Inside of DTS you could have TRANSFORMED just that one column and it would have corrected it for you on the fly. Have had to use that solution many times.





Similar Threads
Thread Thread Starter Forum Replies Last Post
Arabic problem when use upsizing wizard naeem.net SQL Server 2005 1 June 3rd, 2008 02:33 PM
Upsizing. scandalous Access 0 February 5th, 2007 08:48 AM
Upsizing Wizard in Access 2003 isolomon Access 1 January 20th, 2004 06:38 PM
Upsizing problem Dmitriy Pro VB 6 2 November 12th, 2003 10:16 AM
RE: Upsizing wizard sherr8 Access 3 June 9th, 2003 11:34 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.