How to increase the default row size in sql server 2000 only

Hi, Guys.
I am in bit trouble.I am importing the table from mysql to sql server which has having nearly 65000 records.
I starts the import of table by import/export utility.But when the records reaches 65000, the error message came.."THIS TABLE HAVING ROW SIZE 8190 WHICH IS EXCCEDING THE DEFAULT SIZE OF 8060".
So please let me know how to over come this problem..

I CAN'T UPGRADE SQL SERVER SO GIVE SOLUTION FOR SQL SERVER 2000 ONLY...

Thanks in Advance to all of you.

pchadha20For my knowledge it isn't possible to change that limit. You should split your table or in some cases use Ntext-type but that would generate a lot of other troubles.

How to Increase the DB Size

hi,

I have one DB in SQL Server 2005.When I was creating it

takes 7813 MB.Now the databse size almost full.Now I want to extend the

DB Size.At my HDD has more space(near by 160 GB).But I don't know how to

extend the Size.More over I had one doubt.Am executing the

exec sp_helpdb command.It shows the Datafile maxsize is Unlimited.I want to

know when the data is full,whether it automatically takes the size from the

HDD or not.

Please Help me out to this Problem.

When it reaches the maximum capacity, it will be increased automatically. Check whether the Autogrowth enabled or not.sql

How to increase the data file size?

Hi All,

Is it possible to increase the data file size in SQL Server 2005 Express edition?

If yes then how?

Thanks,

Varun

Hi Varun

If you have MSSQL Management Studio installed then from there select Database's properties > Files

There you can setup initial maximum size for Data and Log file.

Thanks,

How to increase table size

Okay, I am actually having 2 problems. We have LANdesk and it uses SQL serve
r
2000 and the people in our desktop department are getting a message which
says:
The size of FixedDrives.Caption is too small. Increase its size by at
least 7.
How do you increase the size of this table.
Problem #2
This is a very recent implementation and I notice that the maintenance plan
will not backup the transaction log. It appears to backup the database ok.
But the transaction log never backs up and it is set to backup every 3 hours
.P#1 : SOund like a column rather than a table problem.
P#2 Did you choode to backup the TLog ? What does SQL Server Agent say ? Is
there a job for this ?
HTH, Jens SUessmeyer.
http://www.sqlserver2005.de
--
"simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com>
schrieb im Newsbeitrag
news:F6473B51-EFE8-4F0D-878A-FEC5404D3E5D@.microsoft.com...
> Okay, I am actually having 2 problems. We have LANdesk and it uses SQL
> server
> 2000 and the people in our desktop department are getting a message which
> says:
> The size of FixedDrives.Caption is too small. Increase its size by at
> least 7.
> How do you increase the size of this table.
> Problem #2
> This is a very recent implementation and I notice that the maintenance
> plan
> will not backup the transaction log. It appears to backup the database ok.
> But the transaction log never backs up and it is set to backup every 3
> hours.|||The error you're getting is from LANdesk, not SQL Server. I suggest you
contact their technical support to see what to do. You can't pre-allocate
space for tables in SQL Server, they automatically grow as you insert more
rows into them.
What recovery mode is the database in? If its simple recovery mode, taking a
log backup is a no-op.
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com> wrote
in message news:F6473B51-EFE8-4F0D-878A-FEC5404D3E5D@.microsoft.com...
> Okay, I am actually having 2 problems. We have LANdesk and it uses SQL
server
> 2000 and the people in our desktop department are getting a message which
> says:
> The size of FixedDrives.Caption is too small. Increase its size by at
> least 7.
> How do you increase the size of this table.
> Problem #2
> This is a very recent implementation and I notice that the maintenance
plan
> will not backup the transaction log. It appears to backup the database ok.
> But the transaction log never backs up and it is set to backup every 3
hours.|||ok, I'm by no means a SQL expert so I'm feeling my way through this and yes
you are rights captions is a column in the fixeddrives table. I right
clicked on the table and chose design table. The captions column data type i
s
char and the length is 60. If I increase it by 7 as the error asks and then
click save, I get a warning during the presave process which goes on to say:
Warning: One or more existing columns have ANSI_PADDING 'off' and will be
re-created with ANSI_PADDING 'on'.
I have no clue what to do from there.
As for the transaction log backup problem, a maintenance plan has been
created to backup the transaction log every 3 hours. It fails everytime. Her
e
are the results:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
'SVRWEBG026' as 'NT AUTHORITY\SYSTEM' (trusted)
Starting maintenance plan 'DB Maintenance Plan2' on 4/18/2005 1:25:00 PM
Backup can not be performed on database 'LDINV'. This sub task is ignored.
End of maintenance plan 'DB Maintenance Plan2' on 4/18/2005 1:25:00 PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
Any help will be greatly appreciated.
"Jens Sü?meyer" wrote:

> P#1 : SOund like a column rather than a table problem.
> P#2 Did you choode to backup the TLog ? What does SQL Server Agent say ? I
s
> there a job for this ?
> HTH, Jens SUessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com>
> schrieb im Newsbeitrag
> news:F6473B51-EFE8-4F0D-878A-FEC5404D3E5D@.microsoft.com...
>
>|||"simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com> wrote
in message news:32826F49-2FBF-48CE-9582-3EC1382455D9@.microsoft.com...
> ok, I'm by no means a SQL expert so I'm feeling my way through this and
> yes
> you are rights captions is a column in the fixeddrives table. I right
> clicked on the table and chose design table. The captions column data type
> is
> char and the length is 60. If I increase it by 7 as the error asks and
> then
> click save, I get a warning during the presave process which goes on to
> say:
You should contact LANDesk Tech Support. Going in and changing the
structure of a database for an application could break the application, or
at the very least, waste a lot of time and space with no positive results.
If their customers have encountered this problem before, they might have a
thoroughly tested fix or patch for the front-end software as well as the
database.|||So, if the database is in simple recovery mode you can not backup the
transaction logs? What can you do to tell what mode it is in? For that matte
r
what are the modes?
Again I'm not the SQL guy.
"Paul S Randal [MS]" wrote:

> The error you're getting is from LANdesk, not SQL Server. I suggest you
> contact their technical support to see what to do. You can't pre-allocate
> space for tables in SQL Server, they automatically grow as you insert more
> rows into them.
> What recovery mode is the database in? If its simple recovery mode, taking
a
> log backup is a no-op.
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com> wrot
e
> in message news:F6473B51-EFE8-4F0D-878A-FEC5404D3E5D@.microsoft.com...
> server
> plan
> hours.
>
>

How to increase table size

Okay, I am actually having 2 problems. We have LANdesk and it uses SQL server
2000 and the people in our desktop department are getting a message which
says:
The size of FixedDrives.Caption is too small. Increase its size by at
least 7.
How do you increase the size of this table.
Problem #2
This is a very recent implementation and I notice that the maintenance plan
will not backup the transaction log. It appears to backup the database ok.
But the transaction log never backs up and it is set to backup every 3 hours.P#1 : SOund like a column rather than a table problem.
P#2 Did you choode to backup the TLog ? What does SQL Server Agent say ? Is
there a job for this ?
HTH, Jens SUessmeyer.
--
http://www.sqlserver2005.de
--
"simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com>
schrieb im Newsbeitrag
news:F6473B51-EFE8-4F0D-878A-FEC5404D3E5D@.microsoft.com...
> Okay, I am actually having 2 problems. We have LANdesk and it uses SQL
> server
> 2000 and the people in our desktop department are getting a message which
> says:
> The size of FixedDrives.Caption is too small. Increase its size by at
> least 7.
> How do you increase the size of this table.
> Problem #2
> This is a very recent implementation and I notice that the maintenance
> plan
> will not backup the transaction log. It appears to backup the database ok.
> But the transaction log never backs up and it is set to backup every 3
> hours.|||The error you're getting is from LANdesk, not SQL Server. I suggest you
contact their technical support to see what to do. You can't pre-allocate
space for tables in SQL Server, they automatically grow as you insert more
rows into them.
What recovery mode is the database in? If its simple recovery mode, taking a
log backup is a no-op.
Regards
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com> wrote
in message news:F6473B51-EFE8-4F0D-878A-FEC5404D3E5D@.microsoft.com...
> Okay, I am actually having 2 problems. We have LANdesk and it uses SQL
server
> 2000 and the people in our desktop department are getting a message which
> says:
> The size of FixedDrives.Caption is too small. Increase its size by at
> least 7.
> How do you increase the size of this table.
> Problem #2
> This is a very recent implementation and I notice that the maintenance
plan
> will not backup the transaction log. It appears to backup the database ok.
> But the transaction log never backs up and it is set to backup every 3
hours.|||ok, I'm by no means a SQL expert so I'm feeling my way through this and yes
you are rights captions is a column in the fixeddrives table. I right
clicked on the table and chose design table. The captions column data type is
char and the length is 60. If I increase it by 7 as the error asks and then
click save, I get a warning during the presave process which goes on to say:
Warning: One or more existing columns have ANSI_PADDING 'off' and will be
re-created with ANSI_PADDING 'on'.
I have no clue what to do from there.
As for the transaction log backup problem, a maintenance plan has been
created to backup the transaction log every 3 hours. It fails everytime. Here
are the results:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
'SVRWEBG026' as 'NT AUTHORITY\SYSTEM' (trusted)
Starting maintenance plan 'DB Maintenance Plan2' on 4/18/2005 1:25:00 PM
Backup can not be performed on database 'LDINV'. This sub task is ignored.
End of maintenance plan 'DB Maintenance Plan2' on 4/18/2005 1:25:00 PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
Any help will be greatly appreciated.
"Jens Sü�meyer" wrote:
> P#1 : SOund like a column rather than a table problem.
> P#2 Did you choode to backup the TLog ? What does SQL Server Agent say ? Is
> there a job for this ?
> HTH, Jens SUessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com>
> schrieb im Newsbeitrag
> news:F6473B51-EFE8-4F0D-878A-FEC5404D3E5D@.microsoft.com...
> > Okay, I am actually having 2 problems. We have LANdesk and it uses SQL
> > server
> > 2000 and the people in our desktop department are getting a message which
> > says:
> >
> > The size of FixedDrives.Caption is too small. Increase its size by at
> > least 7.
> >
> > How do you increase the size of this table.
> >
> > Problem #2
> >
> > This is a very recent implementation and I notice that the maintenance
> > plan
> > will not backup the transaction log. It appears to backup the database ok.
> > But the transaction log never backs up and it is set to backup every 3
> > hours.
>
>|||"simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com> wrote
in message news:32826F49-2FBF-48CE-9582-3EC1382455D9@.microsoft.com...
> ok, I'm by no means a SQL expert so I'm feeling my way through this and
> yes
> you are rights captions is a column in the fixeddrives table. I right
> clicked on the table and chose design table. The captions column data type
> is
> char and the length is 60. If I increase it by 7 as the error asks and
> then
> click save, I get a warning during the presave process which goes on to
> say:
You should contact LANDesk Tech Support. Going in and changing the
structure of a database for an application could break the application, or
at the very least, waste a lot of time and space with no positive results.
If their customers have encountered this problem before, they might have a
thoroughly tested fix or patch for the front-end software as well as the
database.|||So, if the database is in simple recovery mode you can not backup the
transaction logs? What can you do to tell what mode it is in? For that matter
what are the modes?
Again I'm not the SQL guy.
"Paul S Randal [MS]" wrote:
> The error you're getting is from LANdesk, not SQL Server. I suggest you
> contact their technical support to see what to do. You can't pre-allocate
> space for tables in SQL Server, they automatically grow as you insert more
> rows into them.
> What recovery mode is the database in? If its simple recovery mode, taking a
> log backup is a no-op.
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com> wrote
> in message news:F6473B51-EFE8-4F0D-878A-FEC5404D3E5D@.microsoft.com...
> > Okay, I am actually having 2 problems. We have LANdesk and it uses SQL
> server
> > 2000 and the people in our desktop department are getting a message which
> > says:
> >
> > The size of FixedDrives.Caption is too small. Increase its size by at
> > least 7.
> >
> > How do you increase the size of this table.
> >
> > Problem #2
> >
> > This is a very recent implementation and I notice that the maintenance
> plan
> > will not backup the transaction log. It appears to backup the database ok.
> > But the transaction log never backs up and it is set to backup every 3
> hours.
>
>

How to increase table size

Okay, I am actually having 2 problems. We have LANdesk and it uses SQL server
2000 and the people in our desktop department are getting a message which
says:
The size of FixedDrives.Caption is too small. Increase its size by at
least 7.
How do you increase the size of this table.
Problem #2
This is a very recent implementation and I notice that the maintenance plan
will not backup the transaction log. It appears to backup the database ok.
But the transaction log never backs up and it is set to backup every 3 hours.
P#1 : SOund like a column rather than a table problem.
P#2 Did you choode to backup the TLog ? What does SQL Server Agent say ? Is
there a job for this ?
HTH, Jens SUessmeyer.
http://www.sqlserver2005.de
"simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com>
schrieb im Newsbeitrag
news:F6473B51-EFE8-4F0D-878A-FEC5404D3E5D@.microsoft.com...
> Okay, I am actually having 2 problems. We have LANdesk and it uses SQL
> server
> 2000 and the people in our desktop department are getting a message which
> says:
> The size of FixedDrives.Caption is too small. Increase its size by at
> least 7.
> How do you increase the size of this table.
> Problem #2
> This is a very recent implementation and I notice that the maintenance
> plan
> will not backup the transaction log. It appears to backup the database ok.
> But the transaction log never backs up and it is set to backup every 3
> hours.
|||The error you're getting is from LANdesk, not SQL Server. I suggest you
contact their technical support to see what to do. You can't pre-allocate
space for tables in SQL Server, they automatically grow as you insert more
rows into them.
What recovery mode is the database in? If its simple recovery mode, taking a
log backup is a no-op.
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com> wrote
in message news:F6473B51-EFE8-4F0D-878A-FEC5404D3E5D@.microsoft.com...
> Okay, I am actually having 2 problems. We have LANdesk and it uses SQL
server
> 2000 and the people in our desktop department are getting a message which
> says:
> The size of FixedDrives.Caption is too small. Increase its size by at
> least 7.
> How do you increase the size of this table.
> Problem #2
> This is a very recent implementation and I notice that the maintenance
plan
> will not backup the transaction log. It appears to backup the database ok.
> But the transaction log never backs up and it is set to backup every 3
hours.
|||ok, I'm by no means a SQL expert so I'm feeling my way through this and yes
you are rights captions is a column in the fixeddrives table. I right
clicked on the table and chose design table. The captions column data type is
char and the length is 60. If I increase it by 7 as the error asks and then
click save, I get a warning during the presave process which goes on to say:
Warning: One or more existing columns have ANSI_PADDING 'off' and will be
re-created with ANSI_PADDING 'on'.
I have no clue what to do from there.
As for the transaction log backup problem, a maintenance plan has been
created to backup the transaction log every 3 hours. It fails everytime. Here
are the results:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server
'SVRWEBG026' as 'NT AUTHORITY\SYSTEM' (trusted)
Starting maintenance plan 'DB Maintenance Plan2' on 4/18/2005 1:25:00 PM
Backup can not be performed on database 'LDINV'. This sub task is ignored.
End of maintenance plan 'DB Maintenance Plan2' on 4/18/2005 1:25:00 PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
Any help will be greatly appreciated.
"Jens Sü?meyer" wrote:

> P#1 : SOund like a column rather than a table problem.
> P#2 Did you choode to backup the TLog ? What does SQL Server Agent say ? Is
> there a job for this ?
> HTH, Jens SUessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com>
> schrieb im Newsbeitrag
> news:F6473B51-EFE8-4F0D-878A-FEC5404D3E5D@.microsoft.com...
>
>
|||"simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com> wrote
in message news:32826F49-2FBF-48CE-9582-3EC1382455D9@.microsoft.com...
> ok, I'm by no means a SQL expert so I'm feeling my way through this and
> yes
> you are rights captions is a column in the fixeddrives table. I right
> clicked on the table and chose design table. The captions column data type
> is
> char and the length is 60. If I increase it by 7 as the error asks and
> then
> click save, I get a warning during the presave process which goes on to
> say:
You should contact LANDesk Tech Support. Going in and changing the
structure of a database for an application could break the application, or
at the very least, waste a lot of time and space with no positive results.
If their customers have encountered this problem before, they might have a
thoroughly tested fix or patch for the front-end software as well as the
database.
|||So, if the database is in simple recovery mode you can not backup the
transaction logs? What can you do to tell what mode it is in? For that matter
what are the modes?
Again I'm not the SQL guy.
"Paul S Randal [MS]" wrote:

> The error you're getting is from LANdesk, not SQL Server. I suggest you
> contact their technical support to see what to do. You can't pre-allocate
> space for tables in SQL Server, they automatically grow as you insert more
> rows into them.
> What recovery mode is the database in? If its simple recovery mode, taking a
> log backup is a no-op.
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "simpsoro@.webster.edu" <simpsorowebsteredu@.discussions.microsoft.com> wrote
> in message news:F6473B51-EFE8-4F0D-878A-FEC5404D3E5D@.microsoft.com...
> server
> plan
> hours.
>
>
sql

how to increase size of datatype...

Dear

I am using varchar data type in my table.it provides maximum 8000 character. but i want more than that.

how to increase size more than 8000

i want to use text datatype but when i type in length it doenst type.it displays only 16.i cant change to another value.

please help me out

Waiting for reply

Regards,
ASIFTEXT does not take a length the way VARCHAR does

it's just TEXT

how to increase maximum rowsize in sql server 2000

Is there any ways to increase the default maximum row size
of 8060 in SQL server 2000?
Thanks in advance
kiranNo you cannot.
You can however split your table into multiple tables and maintain
relationships between them.
--
HTH,
SriSamp
Please reply to the whole group only!
http://www32.brinkster.com/srisamp
"kiran kumar joseph" <kiran_joseph82@.yahoo.com> wrote in message
news:00f201c3aff4$742ea1c0$a001280a@.phx.gbl...
> Is there any ways to increase the default maximum row size
> of 8060 in SQL server 2000?
> Thanks in advance
> kiran|||Another option is to use text columns instead of varchars.
--
Andrew J. Kelly
SQL Server MVP
"SriSamp" <ssampath@.sct.co.in> wrote in message
news:uLq%23gd$rDHA.1996@.TK2MSFTNGP09.phx.gbl...
> No you cannot.
> You can however split your table into multiple tables and maintain
> relationships between them.
> --
> HTH,
> SriSamp
> Please reply to the whole group only!
> http://www32.brinkster.com/srisamp
> "kiran kumar joseph" <kiran_joseph82@.yahoo.com> wrote in message
> news:00f201c3aff4$742ea1c0$a001280a@.phx.gbl...
> > Is there any ways to increase the default maximum row size
> > of 8060 in SQL server 2000?
> >
> > Thanks in advance
> > kiran
>

How to Increase maximum row size

Hi,
I have an database migration project wherein I need to migrate data from
FileMaker Pro to SQL. The FileMaker Pro stores files as flat files and there
are more than 300 fields in one table. Now when I try to create the same
table structure in SQL, I get the error saying it has reached the maximum ro
w
size of 8060 bytes.
Can anyone let me know is there a way to increase the row size limit. If
yes, then how? Also it would be great if you can let me know whether it is a
good suggestion to increase the row size limit.
Regards,
Sudhakara.T.P.Hello,
In SQL 2005 it is possible and older version its a limitation. See the below
article.
http://searchsqlserver.techtarget.c...1149592,00.html
Thanks
Hari
"Sudhakara.T.P." <SudhakaraTP@.discussions.microsoft.com> wrote in message
news:1B5C4FB3-DB61-4E30-A3F6-8EE6113C623B@.microsoft.com...
> Hi,
> I have an database migration project wherein I need to migrate data from
> FileMaker Pro to SQL. The FileMaker Pro stores files as flat files and
> there
> are more than 300 fields in one table. Now when I try to create the same
> table structure in SQL, I get the error saying it has reached the maximum
> row
> size of 8060 bytes.
> Can anyone let me know is there a way to increase the row size limit. If
> yes, then how? Also it would be great if you can let me know whether it is
> a
> good suggestion to increase the row size limit.
> Regards,
> Sudhakara.T.P.|||"Sudhakara.T.P." <SudhakaraTP@.discussions.microsoft.com> wrote in message
news:1B5C4FB3-DB61-4E30-A3F6-8EE6113C623B@.microsoft.com...
> Hi,
> I have an database migration project wherein I need to migrate data from
> FileMaker Pro to SQL. The FileMaker Pro stores files as flat files and
> there
> are more than 300 fields in one table. Now when I try to create the same
> table structure in SQL, I get the error saying it has reached the maximum
> row
> size of 8060 bytes.
> Can anyone let me know is there a way to increase the row size limit. If
> yes, then how? Also it would be great if you can let me know whether it is
> a
> good suggestion to increase the row size limit.
There is no way to increase this limit. Given that your table has 300
columns, perhaps now is a good time to revisit the database design. It is
likely that this table/database is not properly normalized. At a minimum,
you will need to split the table to overcome the limit.

How to Increase maximum row size

Hi,
I have an database migration project wherein I need to migrate data from
FileMaker Pro to SQL. The FileMaker Pro stores files as flat files and there
are more than 300 fields in one table. Now when I try to create the same
table structure in SQL, I get the error saying it has reached the maximum row
size of 8060 bytes.
Can anyone let me know is there a way to increase the row size limit. If
yes, then how? Also it would be great if you can let me know whether it is a
good suggestion to increase the row size limit.
Regards,
Sudhakara.T.P.Hello,
In SQL 2005 it is possible and older version its a limitation. See the below
article.
http://searchsqlserver.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid87_gci1149592,00.html
Thanks
Hari
"Sudhakara.T.P." <SudhakaraTP@.discussions.microsoft.com> wrote in message
news:1B5C4FB3-DB61-4E30-A3F6-8EE6113C623B@.microsoft.com...
> Hi,
> I have an database migration project wherein I need to migrate data from
> FileMaker Pro to SQL. The FileMaker Pro stores files as flat files and
> there
> are more than 300 fields in one table. Now when I try to create the same
> table structure in SQL, I get the error saying it has reached the maximum
> row
> size of 8060 bytes.
> Can anyone let me know is there a way to increase the row size limit. If
> yes, then how? Also it would be great if you can let me know whether it is
> a
> good suggestion to increase the row size limit.
> Regards,
> Sudhakara.T.P.|||"Sudhakara.T.P." <SudhakaraTP@.discussions.microsoft.com> wrote in message
news:1B5C4FB3-DB61-4E30-A3F6-8EE6113C623B@.microsoft.com...
> Hi,
> I have an database migration project wherein I need to migrate data from
> FileMaker Pro to SQL. The FileMaker Pro stores files as flat files and
> there
> are more than 300 fields in one table. Now when I try to create the same
> table structure in SQL, I get the error saying it has reached the maximum
> row
> size of 8060 bytes.
> Can anyone let me know is there a way to increase the row size limit. If
> yes, then how? Also it would be great if you can let me know whether it is
> a
> good suggestion to increase the row size limit.
There is no way to increase this limit. Given that your table has 300
columns, perhaps now is a good time to revisit the database design. It is
likely that this table/database is not properly normalized. At a minimum,
you will need to split the table to overcome the limit.

How to Increase maximum row size

Hi,
I have an database migration project wherein I need to migrate data from
FileMaker Pro to SQL. The FileMaker Pro stores files as flat files and there
are more than 300 fields in one table. Now when I try to create the same
table structure in SQL, I get the error saying it has reached the maximum row
size of 8060 bytes.
Can anyone let me know is there a way to increase the row size limit. If
yes, then how? Also it would be great if you can let me know whether it is a
good suggestion to increase the row size limit.
Regards,
Sudhakara.T.P.
Hello,
In SQL 2005 it is possible and older version its a limitation. See the below
article.
http://searchsqlserver.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid87_gci1149592,00.html
Thanks
Hari
"Sudhakara.T.P." <SudhakaraTP@.discussions.microsoft.com> wrote in message
news:1B5C4FB3-DB61-4E30-A3F6-8EE6113C623B@.microsoft.com...
> Hi,
> I have an database migration project wherein I need to migrate data from
> FileMaker Pro to SQL. The FileMaker Pro stores files as flat files and
> there
> are more than 300 fields in one table. Now when I try to create the same
> table structure in SQL, I get the error saying it has reached the maximum
> row
> size of 8060 bytes.
> Can anyone let me know is there a way to increase the row size limit. If
> yes, then how? Also it would be great if you can let me know whether it is
> a
> good suggestion to increase the row size limit.
> Regards,
> Sudhakara.T.P.
|||"Sudhakara.T.P." <SudhakaraTP@.discussions.microsoft.com> wrote in message
news:1B5C4FB3-DB61-4E30-A3F6-8EE6113C623B@.microsoft.com...
> Hi,
> I have an database migration project wherein I need to migrate data from
> FileMaker Pro to SQL. The FileMaker Pro stores files as flat files and
> there
> are more than 300 fields in one table. Now when I try to create the same
> table structure in SQL, I get the error saying it has reached the maximum
> row
> size of 8060 bytes.
> Can anyone let me know is there a way to increase the row size limit. If
> yes, then how? Also it would be great if you can let me know whether it is
> a
> good suggestion to increase the row size limit.
There is no way to increase this limit. Given that your table has 300
columns, perhaps now is a good time to revisit the database design. It is
likely that this table/database is not properly normalized. At a minimum,
you will need to split the table to overcome the limit.