Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


If you could stop working tomorrow, would you still do SQL?


If you could stop working tomorrow, would you still do SQL?

Author
Message
gabriel.defigueiredo
gabriel.defigueiredo
Grasshopper
Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)

Group: General Forum Members
Points: 15 Visits: 144
I have a number of interests outside the SQL world, classical and jazz music being some of them. Even then, I would probably tinker around SQL Server and Visual Studio (or whatever they might call it in the eventual years) keeping my development skills as sharp as 'enlightened' age can :-).
Koen Verbeeck
Koen Verbeeck
SSCoach
SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)SSCoach (18K reputation)

Group: General Forum Members
Points: 18763 Visits: 13249
I'd definately travel the world, wacht all those series I wanted to see, play all those games I've wanted to play, but after a few months/years, when the boredom kicks in, I think I would go back to work. With SQL BI of course :-)


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
P Jones
P Jones
Right there with Babe
Right there with Babe (776 reputation)Right there with Babe (776 reputation)Right there with Babe (776 reputation)Right there with Babe (776 reputation)Right there with Babe (776 reputation)Right there with Babe (776 reputation)Right there with Babe (776 reputation)Right there with Babe (776 reputation)

Group: General Forum Members
Points: 776 Visits: 1510
I'd be using MySQL and writing WordPress plugins for my hobby web sites but even then I find SSIS such a useful tool that I can't see me getting away from it completely. I would love to get away from formal paid work as an employee but maybe do the odd little web site or database job for a friend as a freelance. Otherwise I've too many hobbies to want to go to work.
Michael Lysons
Michael Lysons
Ten Centuries
Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)Ten Centuries (1.3K reputation)

Group: General Forum Members
Points: 1326 Visits: 1404
I'm a budding iPhone developer. Specifically, I like to build games. So, all being well, that would be what I would do if I could give up the day job. However, I'd choose SQLite as the storage mechanism because SQL is, well, so fundamentally cool.
Ian Scarlett
Ian Scarlett
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1579 Visits: 6510
I think you're all sad, and need to get a life ;-) (only joking)

If I could give up work, I'd be overjoyed at not having to touch SQL ever again.

I don't dislike working with it, but there are so many other things I would prefer to spend my life doing.

I take bitbucket's point about an active mind staving off Alzhimers, but I think there are more enjoyable ways than SQL of keeping the mind active.



Greg Edwards-268690
Greg Edwards-268690
SSC Eights!
SSC Eights! (931 reputation)SSC Eights! (931 reputation)SSC Eights! (931 reputation)SSC Eights! (931 reputation)SSC Eights! (931 reputation)SSC Eights! (931 reputation)SSC Eights! (931 reputation)SSC Eights! (931 reputation)

Group: General Forum Members
Points: 931 Visits: 8322
It would be a hobby, something I'd continue to play around with.
Along with Sharepoint and Cubes.
But I have to admit, I'd spend more time out on the water.
And enjoy life with less pressures and deadlines.

Greg E
Christopher Field
Christopher Field
SSC-Enthusiastic
SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)

Group: General Forum Members
Points: 165 Visits: 31
I can't say I would use SQL Server as I would probably use one of the open source databases (Most likely PostgreSQL) in my own projects due to price.

But overall I would use SQL for the retrieval/updating of data. SQL is the best domain specific language for data retrieval/manipulation in a relational database that I have come across as of yet. I find it much more expressive than a procedural/object oriented language for data operations. Although, I think the LINQ is a step in the right direction (though for me it is harder to use than pure SQL, even as the expressions look a lot like SQL).

I would not use SQL for business logic, file management, string manipulation, etc. pretty much anything but data retrieval/updating....otherwise it tends to end up a big mess..... Transact-SQL and even Oracle's PL/SQL are crippled compared to almost any object oriented language. Far too many businesses running SQL Server want to put everything in stored procedures, even stuff that shouldn't be. Really there is only so much brain damage concatenating strings to xp_cmdshell and parsing the output for file manipulation that I can take, especially when Java has such a simple, easy to use File class with more controlled error conditions. With the various libraries/facilities for abstractions/string manipulation abilities in most programming language like Java/.NET/Python/Perl/Ruby/etc. I would use them for everything but data retrieval/updating. CHARINDEX, PATEINDEX are pathetic next to the regular expressions in any one of those languages...

Currently with business logic on all the systems I have seen, you end up either with highly efficient cut and paste code all over the place (since if you try to put common expressions in UDF you get a huge performance penalty) or a mass of UDF upon UDF and various stored procedures that add layers of inefficiencies. Even if you do stored procedures right and keep things set oriented, you end up having to build temp tables prior to calling the procedures, or have a ton of process keyed tables to keep track of when calling stored procedures. Also, if you really make functionally cohesive stored procedures, then you have to make multiple passes over a dataset (for example if you have 10 formulas and one procedure for each formula that is 10 passes over the same dataset). If you go the more efficient day with one pass, you end up with one super stored procedure perhaps with many parameters to select which formula to use...but for maintenance this is a horrible situation as now you have 10 reasons to change this one procedure... Procedural and Object Oriented languages are much better at abstracton/code re-use and to me a heck of a lot more maintainable. Really I would abandon SQL for all "off label" uses and the maintenance headache they cause.

Going forward, I would probably create a business rules library in an object oriented language for database access that uses dynamic SQL strings (with parameters to protect against SQL injection of course...). Most likely, I would use Python/Ruby for most things and Java where performance matters for all my business logic/file/string manipulation needs. I might even try to make some iPad/iPhone applications, in which case I will be using SQL to query SQLite. I will definitely play more with NoSQL based solutions as well, however I would almost bet a million dollars that SQL will be around for years to come, and I will be using it and relational databases for my data storage needs well into the next 50 years....

Definitely if I didn't need to work, I could produce quality applications on my own schedule and focus on quality and doing it right. But also if there is brain damage to maintain the application, then I won't do it on my own because it will be too much like my past employment....
jay-h
jay-h
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1142 Visits: 2253
Yes I'd probably continue to do SQL but I'd probably choose to do much more coding (espcially C++).

...

-- FORTRAN manual for Xerox Computers --
Ninja's_RGR'us
Ninja's_RGR'us
SSC-Insane
SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)SSC-Insane (22K reputation)

Group: General Forum Members
Points: 22325 Visits: 9671
Of course, but not 40 hours / week.!
NF Scott Smith
NF Scott Smith
Mr or Mrs. 500
Mr or Mrs. 500 (587 reputation)Mr or Mrs. 500 (587 reputation)Mr or Mrs. 500 (587 reputation)Mr or Mrs. 500 (587 reputation)Mr or Mrs. 500 (587 reputation)Mr or Mrs. 500 (587 reputation)Mr or Mrs. 500 (587 reputation)Mr or Mrs. 500 (587 reputation)

Group: General Forum Members
Points: 587 Visits: 351
My own $0.02, I don't think I'd likely use it anymore.

I like SQL just fine, it's a great tool and I enjoy using it where it works but under the scenario described, I'm out.

I'd spend a lot more time with my kids, as well as cycling, kayaking and travelling, probably learn to sail and drive a rally car.

I really don't see being hands-on with any specific computer technology at that point.

Cheers!
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search