Posted by Erland Sommarskog on 10/02/91 11:55

panic attack (tunc.ovacik@gmail.com) writes:
> CREATE TABLE [nwind].[dbo].[DDD] (
> [Col001] varchar (255) NULL,
> [Col002] varchar (255) NULL,
> [Col003] varchar (255) NULL,
>...
> [Col543] varchar (255) NULL
> )

The table appears somewhat funny. Does the table really reflect your
business rules? 255 * 543 is 138465 and with a maximum row size of
8060 in SQL Server, this is not like to turn out well.

> i also tried "nvarchar" , "ntext" ect. but none of them worked. :((

If you tried 543 ntext columns, I can understand why that fails. A ntext
column has a 16-byte point which is in the the row, and the real data is
elsewhere. 543 * 16 is 8688, so you can't have all those text pointers
on a single row.

Does your input file really have 543 input fields?




--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: Data provider for Oracle and SQL 2005 on 64bit windows.
• Prev in forum: Re: Reclaim disk space after DROP columns
• Thread view: Re: Having Problem While Importing a Text File

[Reply to this message]