SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Why SQL Server?


Why SQL Server?

Author
Message
Steve Jones
Steve Jones
SSC Guru
SSC Guru (147K reputation)SSC Guru (147K reputation)SSC Guru (147K reputation)SSC Guru (147K reputation)SSC Guru (147K reputation)SSC Guru (147K reputation)SSC Guru (147K reputation)SSC Guru (147K reputation)

Group: Administrators
Points: 147165 Visits: 19434
Comments posted to this topic are about the item Why SQL Server?

Follow me on Twitter: @way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Jeff Moden
Jeff Moden
SSC Guru
SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)SSC Guru (216K reputation)

Group: General Forum Members
Points: 216216 Visits: 41986
Heh... my goodness. Why would anyone consider being "stuck" in SQL Server being "stuck"? I actually gave up the front-end world (11 years ago) to work almost exclusively in SQL Server and haven't regretted that decision for even a split second.

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Gary Varga
Gary Varga
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27299 Visits: 6545
I work as a freelance developer (mainly .NET at the moment) so a large part of of that decision is taken away from me as it lies with my clients. Arguable, I agree to take on work that includes SQL Server elements, however, like many I have worked with Oracle, DB2 and various other database technologies (RDBMS and otherwise).

I prefer to work with SQL Server over the other technologies because I enjoy working on a well integrated stack that in the large part "just works" (troll away). There is plenty for me to remember and learn with each contract that to cover too many database technologies might be spreading myself too thinly and would be a disservice to my clients. I like the commonalities across the toolsets. It is also easier to switch between different versions of the same product compared to also having to switch between different products.

How did I get into SQL Server? As a Windows C++ developer I took on a role that required development against SQL Server 7. I had already received a theoretical relational database education so it was about learning the tools and, most importantly, where practice differs from theory. Fortunately, I was working with an experienced DBA who was also a very nice chap. He ripped apart my first database schema design (in part) and pieced it back together in a review in front of me and others BUT he explained why. The review of the next schema I designed was far simpler for him and far more satisfying for me. Clever as well as nice, eh?

As for SQLServerCentral.com, well I could say that I gravitate to fellow reprobates but seriously I had an issue (cannot remember what, why or for whom) and found knowledge here both in the form of articles and from fellow professionals. I love the lighthearted approach of most allowing scathing debates without it becoming personal - although it must be said that sometimes Steve does step in to stop it going too far.

Gaz

-- Stop your grinnin' and drop your linen...they're everywhere!!!
Keith Langmead
Keith Langmead
SSC Veteran
SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)

Group: General Forum Members
Points: 248 Visits: 428
For me it was definitely a case of falling into it. As a Sys Admin, myself and a couple of colleagues had to learn several technologies for a project at work, so we split them between us and I ended up with SQL Server. I think the tenuous reason was that as the person responsible for backups I'd spent time in SQL getting the backups to work, and therefore knew slightly more about it than the others.

I went on to do my 2000 MCDBA, and ever since it seems I've been "the DBA".

I'd still describe myself as a Sysadmin rather than a DBA, since SQL is only part of my job, but I definitely enjoy it. I think what attracts me to it is that many of the parallels between Sysadmin work and DBA work are exactly those things I enjoy most in my job.

I've certainly thought about focusing more on SQL in the future, but aside from that definitely requiring a job change, I'd miss playing with all the other tech!
batgirl
batgirl
SSCrazy
SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)

Group: General Forum Members
Points: 2145 Visits: 1820
I started learning SQL when I was doing entry level tech support at Microsoft Business Solutions for an accounting product. I simply could not have done that job without looking under the hood. Every IT position I've had since then has increased my skill set and knowledge (as well as my curiosity!) about the product.

I'm currently doing project management for an automotive parts manufacturer and SQL Server is a prevalent part of the systems here - getting ready to plan an upgrade to SQL Server 2012.
Bryant McClellan
Bryant McClellan
UDP Broadcaster
UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)UDP Broadcaster (1.4K reputation)

Group: General Forum Members
Points: 1449 Visits: 546
I was doing mainframe FOCUS development when I first met SQL. We were a big red N shop and the W word was not tolerated well. An outcast from another team was put on our team because he wrote VB applications for Win3x. This was when WinNT was first released and SQL Server was at version 4.x. I had the great good fortune to be taught both technologies by Takker (nickname of the outcast). Over the years I moved off the mainframe and began writing .ASP when Visual Interdev went gold. Eventually I started doing VB and then .Net development. But the SQL always came along for the ride. I was fortunate enough about 10 years ago to stop doing interface development and concentrate on SQL development and I couldn't be happier.

A rut is somewhere you don't want to be. I had that problem with interface work. Just not my gig. SQL gives me a solid development environment that crosses many boundaries (TSQL/SSIS/SSRS/SSAS) so there is no reason to be bored. And it is maturing at a faster rate with many new features and technologies in each release so you can always find a new an better way to accomplish something.

------------
Buy the ticket, take the ride. -- Hunter S. Thompson
Sigerson
Sigerson
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: 1069 Visits: 1237
I work as a sole programmer for a law firm doing both ends, front and back. I've been with SQL Server since around 2000. Before that I had experience with Access to start, then Oracle and PL-SQL, and a mercifully short waltz with DB2. Since I met SQL Server and T-SQL, I've never looked back. What other DBMS has this combination of power and extreme reliability? Initially I was handed SQL Server as "the back end" but if I have any choice in the matter, I'll never work with any other database.

Sigerson

"No pressure, no diamonds." - Thomas Carlyle
OCTom
OCTom
SSCarpal Tunnel
SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)

Group: General Forum Members
Points: 4143 Visits: 4152
I have always loved working with the people for whom I develop applications. I have never "loved" a technology. A technology such as SQL Server is a tool to delivering a product. I work in SQL Server now because my employer has it. That has always been the case. Whether I was an employee or a contractor, I always had to adjust to whatever technology was required at the time. I have always looked at that as an opportunity to learn something new.

I have seen the technological flavor of the day come and go many times over the years (30 + years now). I have learned to not get too excited about a given technology or platform. My next flavor of the day adventure coming is android device programming.

I do love learning new things. :-)

Tom
chuckboycejr
chuckboycejr
Grasshopper
Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)

Group: General Forum Members
Points: 10 Visits: 1346
How I got started with SQL Server?

I was a Sybase DBA and the company where I worked was conducting a physical audit and they were powering down physical machines in the hopes of clearing out a server room.

A machine that was incorrectly thought to be not in use was powered down and internal clients complained. The team doing the audit powered the machine back up and logged in and discovered it had a SQL Server install on it.

We did not have a SQL Server DBA and since I was the Sybase DBA it fell into my lap.

I had no client software and we had no installation media for me to install SQL client tools.

I did some googling (or AltaVista or whatever was around back then) and discovered a swiss army knife of a multi-RDBMS client tool called WinSQL.

The sa password was blank so I was able to login with WinSQL using sa and no password.

Thus began my relationship with SQL Server.
hakim.ali
hakim.ali
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: 1311 Visits: 1090
I started off doing software development with Coldfusion and VB6/VB.NET in my first few jobs. Fortunately, the database was always SQL Server. Over time, I just gravitated towards working on the database partly because the job demanded it and partly because I seemed to enjoy working with the database more than the front end. I have had forays into MySQL, and even been offered full-time jobs on MySQL which I turned down. After having worked with both and comparing the two and seeing how much better SQL Server is, I find MySQL development frustrating because SQL Server makes so many things so much easier, and is far far more capable. I also really like the SQL Server community.

Hakim Ali
www.sqlzen.com
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