Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Autogenerated SQL Script to Add Column, Deletes Tables Data

Status
Not open for further replies.
markphsd

markphsd

Programmer
Jun 24, 2002
758
US
I have been using the SQL Script Generated to update multiple databases after changing one.

It seems one or more of the are deleting all of the data from two or three tables in the datbase.

How would I identify which script causes the deletion?

Mark P.
Providing Low Cost Powerful Point of Sale Solutions.
 
Sort by date Sort by votes
well, at the end of each script, you could print the name of the script, then in the messages tab when you run it, you'll see rows affected followed by the name of the script, and just look for the ones with lots of rows...

--------------------
Procrastinate Now!
 
Upvote 0 Downvote
Okay, this is the report:, Let me know what you think, and thanks

Msg 2714, Level 16, State 6, Server CCS, Line 12
There is already an object named 'tblFolders' in the database.
Msg 3902, Level 16, State 1, Server CCS, Line 1
The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.
Msg 170, Level 15, State 1, Server CCS, Line 15
Line 15: Incorrect syntax near 'ParentID'.
Msg 3902, Level 16, State 1, Server CCS, Line 1
The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'tblEmails'.
Warning: The table 'Tmp_tblEmails' has been created but its maximum row size
(10055) 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 'Tmp_tblEmails' has been created but its maximum row size
(10055) 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.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'tblEmails'.
Msg 1913, Level 16, State 1, Server CCS, Line 20
There is already an index on table 'tblProductOrders' named
'IX_tblProductOrders'.
Msg 1913, Level 16, State 1, Server CCS, Line 1
There is already an index on table 'tblProductOrders' named
'IX_tblProductOrders_1'.
Msg 3902, Level 16, State 1, Server CCS, Line 1
The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.
Warning: The table 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'AlarmOn' in table
'dbo.tblProductOrders1' is specified more than once.
Msg 2714, Level 16, State 6, Server CCS, Line 20
There is already an object named 'tblClientICD9' in the database.
Msg 3902, Level 16, State 1, Server CCS, Line 1
The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.
Warning: The table 'tblEmails' has been created but its maximum row size
(10059) 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 'tblEmails' has been created but its maximum row size
(10059) 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 'tblClients' has been created but its maximum row size
(8325) 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 'tblClients' has been created but its maximum row size
(8325) 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.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'MedicareInitialDate'
in table 'dbo.tblClients' is specified more than once.
Warning: The table 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'tblProductOrders' has been created but its maximum row
size (10979) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (10845) 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.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'tblProductOrders'.
Warning: The table 'tblProductOrders' has been created but its maximum row
size (10845) 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 'tblClients' has been created but its maximum row size
(8461) 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 'tblClients' has been created but its maximum row size
(8461) 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.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'ResidenceType' in
table 'dbo.tblClients' is specified more than once.
Warning: The table 'tblProductOrders' has been created but its maximum row
size (10923) 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 'tblProductOrders' has been created but its maximum row
size (10923) 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 'tblClients' has been created but its maximum row size
(8401) 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 'tblClients' has been created but its maximum row size
(8401) 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.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'EmployeerName' in
table 'dbo.tblClients' is specified more than once.
Warning: The table 'tblProductOrders' has been created but its maximum row
size (10935) 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 'tblProductOrders' has been created but its maximum row
size (10935) 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.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'tblCoupons'.
Msg 15248, Level 11, State 1, Server CCS, Procedure sp_rename, Line 163
Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is
wrong.
Msg 15248, Level 11, State 1, Server CCS, Procedure sp_rename, Line 163
Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is
wrong.
Msg 2705, Level 16, State 4, Server CCS, Line 1
Column names in each table must be unique. Column name 'CouponAmount' in table
'dbo.tblCoupons' is specified more than once.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'CouponStartDate' in
table 'dbo.tblCoupons' is specified more than once.
Warning: The table 'tblClients' has been created but its maximum row size
(8333) 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 'tblClients' has been created but its maximum row size
(8333) 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.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'LastAccessed' in table
'dbo.tblClients' is specified more than once.
(260 rows affected)
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'tblSettingsServer'.
Warning: The table 'tblEmails' has been created but its maximum row size
(10059) 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 'tblEmails' has been created but its maximum row size
(10059) 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 'tblEmails' has been created but its maximum row size
(10063) 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 'tblEmails' has been created but its maximum row size
(10063) 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.
Msg 2714, Level 16, State 6, Server CCS, Line 20
There is already an object named 'Table1' in the database.
Msg 1779, Level 16, State 1, Server CCS, Line 1
Table 'Table1' already has a primary key defined on it.
Msg 1750, Level 16, State 1, Server CCS, Line 1
Could not create constraint. See previous errors.
Msg 3902, Level 16, State 1, Server CCS, Line 1
The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.
Msg 15248, Level 11, State 1, Server CCS, Procedure sp_rename, Line 163
Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is
wrong.
Msg 15248, Level 11, State 1, Server CCS, Procedure sp_rename, Line 163
Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is
wrong.
(15 rows affected)
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'tblEmployees'.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'PositiveNegative' in
table 'dbo.tblProductOrderTenderType' is specified more than once.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'PositiveNegative' in
table 'dbo.tblProductOrderTenderType1' is specified more than once.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'ServiceType' in table
'dbo.tblProductOrderTenderType' is specified more than once.
Msg 15248, Level 11, State 1, Server CCS, Procedure sp_rename, Line 163
Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is
wrong.
Msg 15248, Level 11, State 1, Server CCS, Procedure sp_rename, Line 163
Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is
wrong.
Msg 15248, Level 11, State 1, Server CCS, Procedure sp_rename, Line 163
Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is
wrong.
Msg 15248, Level 11, State 1, Server CCS, Procedure sp_rename, Line 163
Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is
wrong.
Msg 15248, Level 11, State 1, Server CCS, Procedure sp_rename, Line 163
Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is
wrong.
Msg 15248, Level 11, State 1, Server CCS, Procedure sp_rename, Line 163
Either the parameter @objname is ambiguous or the claimed @objtype (COLUMN) is
wrong.
Msg 2705, Level 16, State 4, Server CCS, Line 1
Column names in each table must be unique. Column name 'CState' in table
'dbo.tblProductOrderTenderType' is specified more than once.
Warning: The table 'tblClients' has been created but its maximum row size
(8372) 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 'tblClients' has been created but its maximum row size
(8372) 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.
Msg 2705, Level 16, State 4, Server CCS, Line 12
Column names in each table must be unique. Column name 'UPIN' in table
'dbo.tblClients' is specified more than once.
Warning: The table 'tblClients' has been created but its maximum row size
(8419) 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 'tblClients' has been created but its maximum row size
(8419) 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.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'Specialty' in table
'dbo.tblClients' is specified more than once.
Warning: The table 'tblProductOrders' has been created but its maximum row
size (10947) 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 'tblProductOrders' has been created but its maximum row
size (10947) 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.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'AlarmOn' in table
'dbo.tblProductOrders' is specified more than once.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'MedicareAllowable' in
table 'dbo.tblProductOrderDetails' is specified more than once.
Warning: The table 'tblClients' has been created but its maximum row size
(8317) 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 'tblClients' has been created but its maximum row size
(8317) 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 'tblClients' has been created but its maximum row size
(8317) 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 'tblClients' has been created but its maximum row size
(8317) 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 'tblClients' has been created but its maximum row size
(8317) 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 'tblClients' has been created but its maximum row size
(8317) 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 'Tmp_tblClients' has been created but its maximum row size
(8221) 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 'Tmp_tblClients' has been created but its maximum row size
(8221) 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 'Tmp_tblClients' has been created but its maximum row size
(8221) 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 'Tmp_tblClients' has been created but its maximum row size
(8221) 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 'Tmp_tblClients' has been created but its maximum row size
(8221) 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.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'tblClients'.
Warning: The table 'tblClients' has been created but its maximum row size
(8221) 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 'tblClients' has been created but its maximum row size
(8221) 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 'tblClients' has been created but its maximum row size
(8221) 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 'tblClients' has been created but its maximum row size
(8221) 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 'tblClients' has been created but its maximum row size
(8221) 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 'tblClients' has been created but its maximum row size
(8221) 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 'tblClients' has been created but its maximum row size
(8221) 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 'tblClients' has been created but its maximum row size
(8221) 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 'Tmp_tblClients' has been created but its maximum row size
(8251) 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 'Tmp_tblClients' has been created but its maximum row size
(8251) 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 'Tmp_tblClients' has been created but its maximum row size
(8251) 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 'Tmp_tblClients' has been created but its maximum row size
(8251) 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 'Tmp_tblClients' has been created but its maximum row size
(8251) 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.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'tblClients'.
Warning: The table 'tblClients' has been created but its maximum row size
(8251) 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 'tblClients' has been created but its maximum row size
(8251) 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 'tblClients' has been created but its maximum row size
(8251) 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 'tblClients' has been created but its maximum row size
(8251) 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 'tblClients' has been created but its maximum row size
(8251) 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 'tblClients' has been created but its maximum row size
(8251) 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 'tblClients' has been created but its maximum row size
(8251) 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 'tblClients' has been created but its maximum row size
(8251) 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 'Tmp_tblClients' has been created but its maximum row size
(9151) 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 'Tmp_tblClients' has been created but its maximum row size
(9151) 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 'Tmp_tblClients' has been created but its maximum row size
(9151) 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 'Tmp_tblClients' has been created but its maximum row size
(9151) 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 'Tmp_tblClients' has been created but its maximum row size
(9151) 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.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'tblClients'.
Warning: The table 'tblClients' has been created but its maximum row size
(9151) 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 'tblClients' has been created but its maximum row size
(9151) 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 'tblClients' has been created but its maximum row size
(9151) 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 'tblClients' has been created but its maximum row size
(9151) 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 'tblClients' has been created but its maximum row size
(9151) 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 'tblClients' has been created but its maximum row size
(9151) 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 'tblClients' has been created but its maximum row size
(9151) 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 'tblClients' has been created but its maximum row size
(9151) 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 'Tmp_tblClients' has been created but its maximum row size
(9451) 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 'Tmp_tblClients' has been created but its maximum row size
(9451) 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 'Tmp_tblClients' has been created but its maximum row size
(9451) 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 'Tmp_tblClients' has been created but its maximum row size
(9451) 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 'Tmp_tblClients' has been created but its maximum row size
(9451) 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.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'tblClients'.
Warning: The table 'tblClients' has been created but its maximum row size
(9451) 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 'tblClients' has been created but its maximum row size
(9451) 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 'tblProductOrders' has been created but its maximum row
size (11447) 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 'tblProductOrders' has been created but its maximum row
size (11447) 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.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'EventSubject' in table
'dbo.tblProductOrders1' is specified more than once.
Warning: The table 'tblClients' has been created but its maximum row size
(9465) 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 'tblClients' has been created but its maximum row size
(9465) 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.
(5 rows affected)
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'tblStatus'.
Warning: The table 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblClients' has been created but its maximum row size
(9517) 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 'tblClients' has been created but its maximum row size
(9517) 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 'tblProductOrders' has been created but its maximum row
size (11508) 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 'tblProductOrders' has been created but its maximum row
size (11508) 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.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'AlarmDate' in table
'dbo.tblProductOrders' is specified more than once.
Warning: The table 'tblProductOrders' has been created but its maximum row
size (11902) 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 'tblProductOrders' has been created but its maximum row
size (11902) 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.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'EventSubject' in table
'dbo.tblProductOrders' is specified more than once.
Warning: The table 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'tblProductOrders' has been created but its maximum row
size (11499) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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 'Tmp_tblProductOrders' has been created but its maximum row
size (11387) 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.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'tblProductOrders'.
Warning: The table 'tblProductOrders' has been created but its maximum row
size (11387) 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.
Msg 208, Level 16, State 1, Server CCS, Line 1
Invalid object name 'dbo.ParsedModifiers'.
Msg 3701, Level 11, State 5, Server CCS, Line 1
Cannot drop the table 'dbo.ParsedModifiers', because it does not exist in the
system catalog.
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'ParsedModifiers'.
Warning: The table 'tblProductOrders' has been created but its maximum row
size (11800) 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 'tblProductOrders' has been created but its maximum row
size (11800) 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.
Msg 2705, Level 16, State 4, Server CCS, Line 20
Column names in each table must be unique. Column name 'AlarmDate' in table
'dbo.tblProductOrders' is specified more than once.
Msg 3728, Level 16, State 1, Server CCS, Line 1
'DF_tblCompany_ScheduleCheckOnOff_1__57' is not a constraint.
Msg 3727, Level 16, State 1, Server CCS, Line 1
Could not drop constraint. See previous errors.
Msg 3728, Level 16, State 1, Server CCS, Line 1
'DF_tblCompany_Demo_2__57' is not a constraint.
Msg 3727, Level 16, State 1, Server CCS, Line 1
Could not drop constraint. See previous errors.
Msg 2714, Level 16, State 4, Server CCS, Line 1
There is already an object named 'DF__tblCompan__Manag__05D8E0BE' in the
database.
Msg 1750, Level 16, State 1, Server CCS, Line 1
Could not create constraint. See previous errors.
(1 row affected)
Caution: Changing any part of an object name could break scripts and stored
procedures.
The OBJECT was renamed to 'tblCompanyInfo'.
Msg 3902, Level 16, State 1, Server CCS, Line 1
The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.
Warning: The table 'tblProductOrders' has been created but its maximum row
size (11404) 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 'tblProductOrders' has been created but its maximum row
size (11404) 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.


Mark P.
Providing Low Cost Powerful Point of Sale Solutions.
 
Upvote 0 Downvote
>>Okay, this is the report:, Let me know what you think, and thanks.
Mark,
You have some very serious problems here. Let's start with this error.
'exceeds the maximum number of bytes per row (8060)'
Each row may only contain 8060 bytes. SQL will allow to create a table that exceeds that limit but if you try to insert data that exceeds 8060 it is going to fail and you are going to have data integrity problems. I would suggest that you re-evaluate all the tables you recieved this error on.

Next.
'There is already an object named 'DF__tblCompan__Manag__05D8E0BE' in the
database.'

This the default naming convention SQL assigns to defaults. I would recommend that you name your defaults. They are much eassier to manage when you do.

Next.
"The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION."

Somewhere in your scripts you are trying to commit a transaction with actualy beginning the transaction.

I hoped you made a backup of your database before you ran this script.
I would suggest that you restore the database that you ran this script on. Put it back to its original state.

Get rid of that script. Correct your row sizes, re-name your defaults.
I would also run sp_depends on any table that you are changing the name of to make sure you are not breaking any views or procs.

I would then invest in a tool like SQL Change Manager by idera, which will identify and script out the differences between two databases.

- Paul
10qkyfp.gif

- If at first you don't succeed, find out if the loser gets anything.
 
Upvote 0 Downvote
Paul,

Thanks. I noticed those errors, and wasn't worried about the size right now.

What does this mean? " I would recommend that you name your defaults."

Also, The script is affecting two tables adversely: tblProductOrders and tblEmployees. Can you see in the report where this would happen?

Using auto generated scripts reduces a lot of labor if they work properly. Comparing databases wouldn't be necessary if all of the databases come from one source, and all the changes have been made from one source. On the scale we are talking about comparing would add a signifigant amount of time to the updates.

Mark P.
Providing Low Cost Powerful Point of Sale Solutions.
 
Upvote 0 Downvote
However Idera does this: Roll out schema changes to existing databases. So that's great.

But i'd first like to see if we can resolve this in house.

Mark P.
Providing Low Cost Powerful Point of Sale Solutions.
 
Upvote 0 Downvote
>>What does this mean? " I would recommend that you name your defaults."

It looks like you are altering your tables using the SSMS GUI tool instead of TSQL. When you use TSQL you provide a name for your defaults , when you use the GUI it default to some name with meaningless characters.

Here is an example.

Code: 
ALTER TABLE doc_exz
ADD CONSTRAINT col_b_def
DEFAULT 50 FOR column_b


>>Also, The script is affecting two tables adversely: tblProductOrders and tblEmployees. Can you see in the report where this would happen?

Am I correct in assuming that you are creating a table named TMP_tblProductOrders then inserting the data from the old table, dropping the old table and renaming the TMP table to tblProductOrders?

I would look at your insert statement into the TMP table.


Using auto generated scripts reduces a lot of labor if they work properly. Comparing databases wouldn't be necessary if all of the databases come from one source
Click to expand...

This is why you need a tool like SQL Change manager. All of my database changes are made in dev. These changes are then fed to QA and PROD. Being able to compare servers allows me to tell what changes have been promoted and what changes have not been promoted. This is very important since not all changes are promoted at the same time. Once I've identified what needs to be added/removed/updated the tool can make me a script or make the changes.
The alternative it the way you are doing it. Not very pretty and can cause data integrity problems. SQL generated scripts work fine if you're creating a new empty database but there are some problems as you can see with trying to update a database that already has data.

- Paul
10qkyfp.gif

- If at first you don't succeed, find out if the loser gets anything.
 
Upvote 0 Downvote
Another good tool is SQL Compare. But even with the tools to help you out you cannot ever run the resulting script without looking it over because sometimes things need to be run in a specific order (or somethings need to not be run at this moment becasue it is a change not reeady to roll to production) and the script does not alawys know that.

Questions about posting. See faq183-874
 
Upvote 0 Downvote
SQLSister is correct. Unfortionatly, I think the script you have is a huge monster that needs to be run in much smaller pieces.

- Paul
10qkyfp.gif

- If at first you don't succeed, find out if the loser gets anything.
 
Upvote 0 Downvote
What happens is this:

Changes are made and recorded in SQL Server, the script is generated.

The scripts are then written to a batch file. The order of the Script is run in the order that the script was created.

The batch files were run multiple times against test databases, and everything looked okay. But then as more databases were tested after they went into production, errors happened.

So, we'll just have to add versioning to what scripts are to be run.

Mark P.
Providing Low Cost Powerful Point of Sale Solutions.
 
Upvote 0 Downvote
Mark,
Best advise I can give you is to rethink your promotion process. It is causing data integtrity problems for you. It goes well beyond just adding versioning. I would not trust any auto-generated script that had not been manually reviewed and cleared for release to prod.

- Paul
10qkyfp.gif

- If at first you don't succeed, find out if the loser gets anything.
 
Upvote 0 Downvote
And never ever under any circumstances run a script like this without creating a backup first.

If this script is using a lot of drop table and recreate table statments in it, those need to be rethought as much as possible as well. as your tables get large, this become very impractical in terms of time to run. Sounds like right now it dropped the table and then bombed onthe create table process or the process to refill the table withthe exisiting data. Or there was no process inthe script to put the data back in. If you have to drop a table and recreate it, then the data needs to be in a temp table while that is happening and specific code must be there to resotre the data.

of course a quick glance at your errors also tells me that your table structures are severly flawed. YOu have way toomany tables which exceed the maximum row size. TYou do understand why this is a bd thing don;t you?

Questions about posting. See faq183-874
 
Upvote 0 Downvote
I do, i'm looking at where there are fields that would create excessive size.

However, fortunately for now there is limited interface that would allow a user to exceed this size.

(And although there are many notifications it's only one or two tables that exceeds the size, there are multiple scripts that affect those tables and generate that report error.)

Mark P.
Providing Low Cost Powerful Point of Sale Solutions.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

coorsman
  • Locked
  • Question
Column Data Type. 2
Replies
9
Views
894
Chris Miller
Chris Miller
MathiasB
  • Question
Parameterised sql server query
Replies
8
Views
385
Chriss Miller
C
grnzbra
  • Locked
  • Question
How Do I Add Column to Middle of Table
Replies
4
Views
875
BobSuruncle
BobSuruncle
V
  • Locked
  • Question
xp_cmdshell vs psexec - this SQL server forgets credential to an W10 share
Replies
0
Views
758
Volvere
V
Cpreston
  • Locked
  • Question
How to add a Letter to datepart
Replies
5
Views
770
Andrzejek
Andrzejek

Part and Inventory Search

Sponsor

Back
Top