Time for a consultant

  • Ours seem to be a mix. Sometimes I'll see all parameters defined as varchar(8000), other times there are varchar set at the string length ( varchar(23) )

    (@DerivedTable01_STATUS10 varchar(8000),@DerivedTable01_STATUS21 varchar(8000),@DerivedTable01_STATUS32 varchar(8000),@DerivedTable01_STATUS43 varchar(8000),@DerivedTable01_STATUS54 varchar(8000),@DerivedTable01_SERVICE_REQUEST_STATUS75 varchar(8000),@DerivedTable01_REQUEST_TRANSACTION_TYPE96 varchar(8000),@DerivedTable01_REQUEST_TRANSACTION_TYPE107 varchar(8000),@DerivedTable01_REQUEST_TRANSACTION_TYPE118 varchar(8000),@DerivedTable01_PRINT_REQUEST_ID139 int,@DerivedTable01_SERVICE_REQUEST_STATUS1510 varchar(8000),@DerivedTable01_REQUEST_TRANSACTION_TYPE1711 varchar(8000),@DerivedTable01_REQUEST_TRANSACTION_TYPE1812 varchar(8000),@DerivedTable01_REQUEST_TRANSACTION_TYPE1913 varchar(8000),@DerivedTable01_PRINT_REQUEST_ID2114 int,@DerivedTable01_STATUS2415 varchar(8000),@DerivedTable01_2516 varchar(23),@DerivedTable01_STATUS2717 varchar(8000),@DerivedTable01_2818 varchar(21),@DerivedTable01_STATUS3019 varchar(8000),@DerivedTable01_3120 varchar(23),@DerivedTable01_STATUS3321 varchar(8000),@DerivedTable01_3422 varchar(30),@DerivedTable01_STATUS3623 varchar(8000),@DerivedTable01_3724 varchar(32),@DerivedTable01_LAST_MOD_DATE_TIME4025 datetime,@DerivedTable01_LAST_MODIFIER4226 int)

  • Indianrock (11/29/2016)


    Ours seem to be a mix. Sometimes I'll see all parameters defined as varchar(8000), other times there are varchar set at the string length ( varchar(23) )

    Both of those are the result of developers that aren't putting in time to write proper code.

    Here's a Guruism for you, and I have seen it play out time and time again:

    Anything that allows developers to slap together code more quickly is inversely proportional to the performance and scalability you will get from that code.

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • TheSQLGuru (11/29/2016)


    Anything that allows developers to slap together code more quickly is inversely proportional to the performance and scalability you will get from that code.

    Loved this phrase.

    Luis C.
    General Disclaimer:
    Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

    How to post data/code on a forum to get the best help: Option 1 / Option 2
  • Luis Cazares (11/29/2016)


    TheSQLGuru (11/29/2016)


    Anything that allows developers to slap together code more quickly is inversely proportional to the performance and scalability you will get from that code.

    Loved this phrase.

    Glad you liked it Luis! I have come up with a couple of such "Guruisms" during the last 2 decades of consulting on SQL Server. 😎

    It is amazing how true and applicable this one is though, and at ALL levels too. Regular folk work to get data processing down from hours to minutes or minutes to seconds. At the other end of the spectrum Google and Facebook et al work hard to shave off a millisecond or even smaller time increments from suboptimal constructs.

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

Viewing 4 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic. Login to reply