SQL 2005 Import / Export wizard

Hi,

Our company has just switched from SQL 2000 Enterprise Manager to SQL 2005 Server Management Studio.  My problem is when I try to import or export certain tables I get the error message below.  But when using SQL 2000 EM there is no problems or issues.  

I am exporting tables from SQL 2005 to a blank Access 2000 db.  If I use SQL 2000 EM, exporting the same tables it works just fine.  The error indicates that there is a length limitation of 4000.  I know it's not the blank Access db because I've confirmed that Access 2000 can go up to 63,000 or so.  

Is there a setting within SQL 2005 that needs to be adjusted to allow tables over 4000 in length.  The tables I am having trouble with shows 8,000 length.  I also have the same problem with Importing.

I've tried Importing / Exporting from both the server itself and remotely with the same failed result.

This has had to of happen to others right?  I hope someone can help!  Below is the error message.....

Could not connect destination component.

Error 0xc0204016: DTS.Pipeline: The "output column "Facts_of_Case" (1657)" has a length that is not valid. The length must be between 0 and 4000.
colemac72Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

brad2575Commented:
The error is not saying the table length is over 4000 but the field "Facts_of_Case" is over 4000.  

What is the data type for this field in SQL 2000?  What is it in 2005?  I am thinking in 2000 is is varchar and 2005 may be nvarchar?

What is the data type in Access you are trying to put it in?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
colemac72Author Commented:
The data type in SQL2000   Fact_of_Case is varchar and the size is 8000 and allow nulls is checked

This is same in sql2005     Fact_of_Case is varchar and the size is 8000 and allow nulls is checked

Access is - Memo

Thank you!
0
David ToddSenior DBACommented:
Hi,

The Access Memo will correspond to the Text data type in SQL 2000 and SQL 2005.

Why not transfer data between the two servers directly? Why go through Access?

Cheers
  David
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

colemac72Author Commented:
Hi Dtodd,

We actually moved to a new web host and that's why I currently have both SQL 2000 and 2005.  As of tomorrow we will no longer have the SQL 2000 server.  The reason I mentioned SQL 2000 is I was able to export to Access for years with out a problem on SQL 2000.  Now that we are using 2005 A lot of are tables are getting that error message.  

Is there a setting in sql 2005 that can be changed so it can handle the length over 4000?  I just don't understand why SQL 2000 can do it but 2005 can't?  

Any suggestions would really be appreciated !!
0
David ToddSenior DBACommented:
Hi,

Just a thought, have you upgraded Access? Might be worth a crack. (That is, get a version of Access that knows about SQL 2005) Only try this if easily done.

Maybe customise the export as a DTS package, and use a query to put limits on the field sizes by doing left( field, 2000 )

HTH
  David
0
Mark WillsTopic AdvisorCommented:
Would be inclined to map memo to text. Think you will find that memo is regarded a unicode data type so it is restricted to 2 bytes per character - hence the > 4000 message. Also think you will find it is to do with the drivers. Can try changing the column to varchar(max), or, nvarchar(max).
0
jermaingCommented:
I have moved past this my changing the the nvarchar and using max for the limit.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.