|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Table creation warning concernI am utilizing the June 2005 PPEL and I am logging exceptions to a SQL Server
2000 database. In the PPEL installation there is a script named LoggingDatabse.sql that creates the necessary table and stored procedure. When I execute this script I am getting the following warning: Warning: The table 'Log' has been created but its maximum row size (18000) 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. The reason I am concerned about this is our customer will recycle our application or at the least as for a detailed explanation on this warning. Can anyone explain why this warning occurs and what risk are invoved? I found the following KB: http://support.microsoft.com/kb/260418/en-us however I still need to undertand why this script was shipped as part of the PPEL with the potential of a failure on an insert/update so I can explain in detail to the customer when I am asked. That means the sum of your column sizes exceeds the maximum row size. I ran
into this problem recently and corrected it by decreasing column sizes. Charlie Show quote "Steven" <StevenSw@community.nospam> wrote in message news:8C4A69D2-4477-4C94-9902-4D434520AABE@microsoft.com... >I am utilizing the June 2005 PPEL and I am logging exceptions to a SQL >Server > 2000 database. In the PPEL installation there is a script named > LoggingDatabse.sql that creates the necessary table and stored procedure. > When I execute this script I am getting the following warning: > > Warning: The table 'Log' has been created but its maximum row size (18000) > 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. > > The reason I am concerned about this is our customer will recycle our > application or at the least as for a detailed explanation on this warning. > > Can anyone explain why this warning occurs and what risk are invoved? I > found the following KB: http://support.microsoft.com/kb/260418/en-us > however > I still need to undertand why this script was shipped as part of the PPEL > with the potential of a failure on an insert/update so I can explain in > detail to the customer when I am asked. Yes I understand the warning and the approach to fix it however I was curious
why this script would ship with the June 2005 PPEL with such a warning and what the risks would be if I did in fact decrease the column sizes. Show quote "Charlie@CBFC" wrote: > That means the sum of your column sizes exceeds the maximum row size. I ran > into this problem recently and corrected it by decreasing column sizes. > > Charlie > > "Steven" <StevenSw@community.nospam> wrote in message > news:8C4A69D2-4477-4C94-9902-4D434520AABE@microsoft.com... > >I am utilizing the June 2005 PPEL and I am logging exceptions to a SQL > >Server > > 2000 database. In the PPEL installation there is a script named > > LoggingDatabse.sql that creates the necessary table and stored procedure. > > When I execute this script I am getting the following warning: > > > > Warning: The table 'Log' has been created but its maximum row size (18000) > > 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. > > > > The reason I am concerned about this is our customer will recycle our > > application or at the least as for a detailed explanation on this warning. > > > > Can anyone explain why this warning occurs and what risk are invoved? I > > found the following KB: http://support.microsoft.com/kb/260418/en-us > > however > > I still need to undertand why this script was shipped as part of the PPEL > > with the potential of a failure on an insert/update so I can explain in > > detail to the customer when I am asked. > > > I was lucky enough to catch it in design stage. However damage may already
be done as data that exceeded max row size is truncated. Show quote "Steven" <StevenSw@community.nospam> wrote in message news:94C243E8-9528-45BA-A7BB-4CDDF282F863@microsoft.com... > Yes I understand the warning and the approach to fix it however I was > curious > why this script would ship with the June 2005 PPEL with such a warning and > what the risks would be if I did in fact decrease the column sizes. > > "Charlie@CBFC" wrote: > >> That means the sum of your column sizes exceeds the maximum row size. I >> ran >> into this problem recently and corrected it by decreasing column sizes. >> >> Charlie >> >> "Steven" <StevenSw@community.nospam> wrote in message >> news:8C4A69D2-4477-4C94-9902-4D434520AABE@microsoft.com... >> >I am utilizing the June 2005 PPEL and I am logging exceptions to a SQL >> >Server >> > 2000 database. In the PPEL installation there is a script named >> > LoggingDatabse.sql that creates the necessary table and stored >> > procedure. >> > When I execute this script I am getting the following warning: >> > >> > Warning: The table 'Log' has been created but its maximum row size >> > (18000) >> > 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. >> > >> > The reason I am concerned about this is our customer will recycle our >> > application or at the least as for a detailed explanation on this >> > warning. >> > >> > Can anyone explain why this warning occurs and what risk are invoved? I >> > found the following KB: http://support.microsoft.com/kb/260418/en-us >> > however >> > I still need to undertand why this script was shipped as part of the >> > PPEL >> > with the potential of a failure on an insert/update so I can explain in >> > detail to the customer when I am asked. >> >> >> >I was lucky enough to catch it in design stage. However damage may already Data will not be truncated as a result of exceeding the max row size. The >be done as data that exceeded max row size is truncated. INSERT or UPDATE will fail in that situation. -- Show quoteHope this helps. Dan Guzman SQL Server MVP "Charlie@CBFC" <fineblu***@verizon.net> wrote in message news:%23K8vKi1TGHA.4608@tk2msftngp13.phx.gbl... >I was lucky enough to catch it in design stage. However damage may already >be done as data that exceeded max row size is truncated. > "Steven" <StevenSw@community.nospam> wrote in message > news:94C243E8-9528-45BA-A7BB-4CDDF282F863@microsoft.com... >> Yes I understand the warning and the approach to fix it however I was >> curious >> why this script would ship with the June 2005 PPEL with such a warning >> and >> what the risks would be if I did in fact decrease the column sizes. >> >> "Charlie@CBFC" wrote: >> >>> That means the sum of your column sizes exceeds the maximum row size. I >>> ran >>> into this problem recently and corrected it by decreasing column sizes. >>> >>> Charlie >>> >>> "Steven" <StevenSw@community.nospam> wrote in message >>> news:8C4A69D2-4477-4C94-9902-4D434520AABE@microsoft.com... >>> >I am utilizing the June 2005 PPEL and I am logging exceptions to a SQL >>> >Server >>> > 2000 database. In the PPEL installation there is a script named >>> > LoggingDatabse.sql that creates the necessary table and stored >>> > procedure. >>> > When I execute this script I am getting the following warning: >>> > >>> > Warning: The table 'Log' has been created but its maximum row size >>> > (18000) >>> > 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. >>> > >>> > The reason I am concerned about this is our customer will recycle our >>> > application or at the least as for a detailed explanation on this >>> > warning. >>> > >>> > Can anyone explain why this warning occurs and what risk are invoved? >>> > I >>> > found the following KB: http://support.microsoft.com/kb/260418/en-us >>> > however >>> > I still need to undertand why this script was shipped as part of the >>> > PPEL >>> > with the potential of a failure on an insert/update so I can explain >>> > in >>> > detail to the customer when I am asked. >>> >>> >>> > > To get back to my original question why would this script ship which this
potential failure and what risk are involved if I modify the script so this warning is resolved? Once again I may have to explain this warning in details along with the posibility of an INSERT or UPDATE failure occuring. Show quote "Dan Guzman" wrote: > >I was lucky enough to catch it in design stage. However damage may already > >be done as data that exceeded max row size is truncated. > > Data will not be truncated as a result of exceeding the max row size. The > INSERT or UPDATE will fail in that situation. > > -- > Hope this helps. > > Dan Guzman > SQL Server MVP > > "Charlie@CBFC" <fineblu***@verizon.net> wrote in message > news:%23K8vKi1TGHA.4608@tk2msftngp13.phx.gbl... > >I was lucky enough to catch it in design stage. However damage may already > >be done as data that exceeded max row size is truncated. > > "Steven" <StevenSw@community.nospam> wrote in message > > news:94C243E8-9528-45BA-A7BB-4CDDF282F863@microsoft.com... > >> Yes I understand the warning and the approach to fix it however I was > >> curious > >> why this script would ship with the June 2005 PPEL with such a warning > >> and > >> what the risks would be if I did in fact decrease the column sizes. > >> > >> "Charlie@CBFC" wrote: > >> > >>> That means the sum of your column sizes exceeds the maximum row size. I > >>> ran > >>> into this problem recently and corrected it by decreasing column sizes. > >>> > >>> Charlie > >>> > >>> "Steven" <StevenSw@community.nospam> wrote in message > >>> news:8C4A69D2-4477-4C94-9902-4D434520AABE@microsoft.com... > >>> >I am utilizing the June 2005 PPEL and I am logging exceptions to a SQL > >>> >Server > >>> > 2000 database. In the PPEL installation there is a script named > >>> > LoggingDatabse.sql that creates the necessary table and stored > >>> > procedure. > >>> > When I execute this script I am getting the following warning: > >>> > > >>> > Warning: The table 'Log' has been created but its maximum row size > >>> > (18000) > >>> > 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. > >>> > > >>> > The reason I am concerned about this is our customer will recycle our > >>> > application or at the least as for a detailed explanation on this > >>> > warning. > >>> > > >>> > Can anyone explain why this warning occurs and what risk are invoved? > >>> > I > >>> > found the following KB: http://support.microsoft.com/kb/260418/en-us > >>> > however > >>> > I still need to undertand why this script was shipped as part of the > >>> > PPEL > >>> > with the potential of a failure on an insert/update so I can explain > >>> > in > >>> > detail to the customer when I am asked. > >>> > >>> > >>> > > > > > > > > To get back to my original question why would this script ship which this I'm not sure that I understand what you mean by 'ship' since enterprise > potential failure and what risk are involved if I modify the script so > this > warning is resolved? library application blocks are not a product. Perhaps someone more familiar with the exception logging application block can jump in and authoritatively answer your question. I can't comment on the row size warning or the impact on exceeding the row size without examining the schema and source code <http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/entlib.asp>. It could be that the app is designed in such a was as to ensure the max row size can't be exceeded. It might also be that SQL exceptions during exception logging are handled gracefully and will not cause other problems. IMHO, it's better to ignore the warning message than to change the table schema. -- Show quoteHope this helps. Dan Guzman SQL Server MVP "Steven" <StevenSw@community.nospam> wrote in message news:48757AC6-5226-4A30-8CDE-F603AAE36185@microsoft.com... > To get back to my original question why would this script ship which this > potential failure and what risk are involved if I modify the script so > this > warning is resolved? > > Once again I may have to explain this warning in details along with the > posibility of an INSERT or UPDATE failure occuring. > > "Dan Guzman" wrote: > >> >I was lucky enough to catch it in design stage. However damage may >> >already >> >be done as data that exceeded max row size is truncated. >> >> Data will not be truncated as a result of exceeding the max row size. >> The >> INSERT or UPDATE will fail in that situation. >> >> -- >> Hope this helps. >> >> Dan Guzman >> SQL Server MVP >> >> "Charlie@CBFC" <fineblu***@verizon.net> wrote in message >> news:%23K8vKi1TGHA.4608@tk2msftngp13.phx.gbl... >> >I was lucky enough to catch it in design stage. However damage may >> >already >> >be done as data that exceeded max row size is truncated. >> > "Steven" <StevenSw@community.nospam> wrote in message >> > news:94C243E8-9528-45BA-A7BB-4CDDF282F863@microsoft.com... >> >> Yes I understand the warning and the approach to fix it however I was >> >> curious >> >> why this script would ship with the June 2005 PPEL with such a warning >> >> and >> >> what the risks would be if I did in fact decrease the column sizes. >> >> >> >> "Charlie@CBFC" wrote: >> >> >> >>> That means the sum of your column sizes exceeds the maximum row size. >> >>> I >> >>> ran >> >>> into this problem recently and corrected it by decreasing column >> >>> sizes. >> >>> >> >>> Charlie >> >>> >> >>> "Steven" <StevenSw@community.nospam> wrote in message >> >>> news:8C4A69D2-4477-4C94-9902-4D434520AABE@microsoft.com... >> >>> >I am utilizing the June 2005 PPEL and I am logging exceptions to a >> >>> >SQL >> >>> >Server >> >>> > 2000 database. In the PPEL installation there is a script named >> >>> > LoggingDatabse.sql that creates the necessary table and stored >> >>> > procedure. >> >>> > When I execute this script I am getting the following warning: >> >>> > >> >>> > Warning: The table 'Log' has been created but its maximum row size >> >>> > (18000) >> >>> > 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. >> >>> > >> >>> > The reason I am concerned about this is our customer will recycle >> >>> > our >> >>> > application or at the least as for a detailed explanation on this >> >>> > warning. >> >>> > >> >>> > Can anyone explain why this warning occurs and what risk are >> >>> > invoved? >> >>> > I >> >>> > found the following KB: >> >>> > http://support.microsoft.com/kb/260418/en-us >> >>> > however >> >>> > I still need to undertand why this script was shipped as part of >> >>> > the >> >>> > PPEL >> >>> > with the potential of a failure on an insert/update so I can >> >>> > explain >> >>> > in >> >>> > detail to the customer when I am asked. >> >>> >> >>> >> >>> >> > >> > >> >> >>  |
|||||||||||||||||||||||
Other interesting topics