June 18, 2005 at 2:08 am
Hi...
I'm facing problem with SQL Server 2000, We sent the script file generated using Enterprise Manager to our client, while they running the same they got warning message as follows,
The CREATE DATABASE process is allocating 16.00 MB on disk 'OTISLIVE_Data'.
The CREATE DATABASE process is allocating 17.00 MB on disk 'OTISLIVE_Log'.
'otis' added to role 'db_owner'.
Granted database access to 'otis'.
'otis' added to role 'db_owner'.
Warning: The table 'tabJobDescription' has been created but its maximum row size (20323) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'tabManagmentReview' has been created but its maximum row size (18060) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'tabQIIssues' has been created but its maximum row size (8308) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'tabQIIssuesLineItemsInfo' has been created but its maximum row size (10682) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'tabManagmentReview' has been created but its maximum row size (18060) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'tabQIIssuesLineItemsInfo' has been created but its maximum row size (10682) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'tabJobDescription' has been created but its maximum row size (20323) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'tabQIIssues' has been created but its maximum row size (8308) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'tabJobDescription' has been created but its maximum row size (20323) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'tabQIIssues' has been created but its maximum row size (8308) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'tabQIIssuesLineItemsInfo' has been created but its maximum row size (10682) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
we thought it won't make much impact on data, but we are now facing problem while porting the data from Access to SQL Server on these tables, upto 10000 rows inserted into table without problem, after that none of the rows inserted into the table & deleted from the table.
How to over come this situation? what property in SQL Server or Table to be changed to accomodate all the rows(more than 10000, since we have millions of rows in access tables).
regards,
Srinivasan V
June 18, 2005 at 2:20 am
common problem read these
http://communityserver.org/forums/ShowPost.aspx?PostID=465908
http://www.mcse.ms/archive93-2004-5-705121.html
My Blog:
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply