Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. The Soapbox
  4. sql maintaince hell?

sql maintaince hell?

Scheduled Pinned Locked Moved The Soapbox
databasesysadminquestion
11 Posts 7 Posters 2 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • W Offline
    W Offline
    wolfbinary
    wrote on last edited by
    #1

    How is having sql queries in code and stored procedures on the server make for good maintenance? Now you have two places to look for things to go wrong. :wtf:

    D M 2 Replies Last reply
    0
    • W wolfbinary

      How is having sql queries in code and stored procedures on the server make for good maintenance? Now you have two places to look for things to go wrong. :wtf:

      D Offline
      D Offline
      Distind
      wrote on last edited by
      #2

      Because they used to have some in the asp.net markup, now there's only 2 places to look rather than three. I say this from experience.

      W 1 Reply Last reply
      0
      • D Distind

        Because they used to have some in the asp.net markup, now there's only 2 places to look rather than three. I say this from experience.

        W Offline
        W Offline
        wolfbinary
        wrote on last edited by
        #3

        Only this is for asp.net applications built from scratch. I'm thinking future maintenance. You're explanation offers at least a little bit of incite.

        D H 2 Replies Last reply
        0
        • W wolfbinary

          Only this is for asp.net applications built from scratch. I'm thinking future maintenance. You're explanation offers at least a little bit of incite.

          D Offline
          D Offline
          Distind
          wrote on last edited by
          #4

          Ah, Well, I'm actually falling off the two location band wagon at the moment myself. My general thought was, it's a pain to sort through a few hundred stored procedures so just keep the little stuff in the code itself. Which works at first, then you wind up with a few fifty stored procedures and a few fifty in code procedures once the customer starts making requests beyond your initial design.

          T 1 Reply Last reply
          0
          • D Distind

            Ah, Well, I'm actually falling off the two location band wagon at the moment myself. My general thought was, it's a pain to sort through a few hundred stored procedures so just keep the little stuff in the code itself. Which works at first, then you wind up with a few fifty stored procedures and a few fifty in code procedures once the customer starts making requests beyond your initial design.

            T Offline
            T Offline
            The Man from U N C L E
            wrote on last edited by
            #5

            Put it all in SQL I say. We started out with some stuff in code and some in SQL, but as the number of procedures in our app now exceeds 3000 I am glad we are all in SQL now!

            If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles]  [My Website]

            D 1 Reply Last reply
            0
            • T The Man from U N C L E

              Put it all in SQL I say. We started out with some stuff in code and some in SQL, but as the number of procedures in our app now exceeds 3000 I am glad we are all in SQL now!

              If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles]  [My Website]

              D Offline
              D Offline
              Distind
              wrote on last edited by
              #6

              Seems to be the best way despite the couple of problems I've had in the past(five people trying to work on something that only has 2 connections was fun), but none of the issues have ever been the SQL so much as the IT...

              J 1 Reply Last reply
              0
              • D Distind

                Seems to be the best way despite the couple of problems I've had in the past(five people trying to work on something that only has 2 connections was fun), but none of the issues have ever been the SQL so much as the IT...

                J Offline
                J Offline
                Joe Simes
                wrote on last edited by
                #7

                Place I work at requires that we have our procs in the database wrapped for security purposes. So three places for me, in database, in code and *.sql files in my dev directory (the unwrapped source from the database)! :wtf:

                1 Reply Last reply
                0
                • W wolfbinary

                  How is having sql queries in code and stored procedures on the server make for good maintenance? Now you have two places to look for things to go wrong. :wtf:

                  M Offline
                  M Offline
                  Mycroft Holmes
                  wrote on last edited by
                  #8

                  Oh not at all now you can have them as LINQ statements as well so you have no idea what sort of code is hitting your database. Almost as silly as have clr in you database, heres another though don't just use result sets do 50% as xml results as well. Rip the frikkin lot out of the code, stick em all into procs. Have the next idiot that presents LINQ as a solution shot as an example. Oh wait why not put you linq into the cloud AAaaaahhhhhhhhh

                  Never underestimate the power of human stupidity RAH

                  B 1 Reply Last reply
                  0
                  • W wolfbinary

                    Only this is for asp.net applications built from scratch. I'm thinking future maintenance. You're explanation offers at least a little bit of incite.

                    H Offline
                    H Offline
                    hairy_hats
                    wrote on last edited by
                    #9

                    Incite and insight are quite different. :-D

                    I hope you realise that hamsters are very creative when it comes to revenge. - Elaine

                    1 Reply Last reply
                    0
                    • M Mycroft Holmes

                      Oh not at all now you can have them as LINQ statements as well so you have no idea what sort of code is hitting your database. Almost as silly as have clr in you database, heres another though don't just use result sets do 50% as xml results as well. Rip the frikkin lot out of the code, stick em all into procs. Have the next idiot that presents LINQ as a solution shot as an example. Oh wait why not put you linq into the cloud AAaaaahhhhhhhhh

                      Never underestimate the power of human stupidity RAH

                      B Offline
                      B Offline
                      Brady Kelly
                      wrote on last edited by
                      #10

                      Do I detect some issues with LINQ? :laugh:

                      M 1 Reply Last reply
                      0
                      • B Brady Kelly

                        Do I detect some issues with LINQ? :laugh:

                        M Offline
                        M Offline
                        Mycroft Holmes
                        wrote on last edited by
                        #11

                        Yup I have issues with linq! Stupid frikkin bloody idea thought up by Microsofts over technified geeks and inflicted on the poor bloody developer community. The miserable SOB who thought of this should be taken out and shot, boiled in oil, drawn and quartered and drowned in butter. Then deep fry the bastard. Just what we need another abstraction layer!!!!!!!

                        Never underestimate the power of human stupidity RAH

                        1 Reply Last reply
                        0
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • World
                        • Users
                        • Groups