Comments on: Starting the SQL Journey http://www.brentozar.com/archive/2009/04/starting-the-sql-journey/ Your technology pain-relief experts. Wed, 08 Feb 2012 16:37:59 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Janice http://www.brentozar.com/archive/2009/04/starting-the-sql-journey/comment-page-1/#comment-16952 Janice Fri, 22 Jan 2010 21:12:39 +0000 http://www.brentozar.com/?p=3466#comment-16952 "I ran the network cables, I fixed the printers, I installed the OS’s, bought the desktops, yadda yadda yadda" Exactly where I'm at and where I've been the past years. Touched a database here and there...but never really administered a "real" one!Frustrating. What again do they say about the difference between a jack of all trades and an expert...? Oh yeah..."One knows more and more about less and less until he knows everything about nothing. The other knows less and less about more and more until he knows nothing about everything." Ouch. I like your post, it's inspiring. “I ran the network cables, I fixed the printers, I installed the OS’s, bought the desktops, yadda yadda yadda”
Exactly where I’m at and where I’ve been the past years. Touched a database here and there…but never really administered a “real” one!Frustrating. What again do they say about the difference between a jack of all trades and an expert…? Oh yeah…”One knows more and more about less and less until he knows everything about nothing. The other knows less and less about more and more until he knows nothing about everything.” Ouch.

I like your post, it’s inspiring.

]]> By: Colin http://www.brentozar.com/archive/2009/04/starting-the-sql-journey/comment-page-1/#comment-11081 Colin Tue, 08 Sep 2009 17:18:40 +0000 http://www.brentozar.com/?p=3466#comment-11081 I agree that it is not cool to have to learn a new language all the time and that is one reason that I have never had any interest in becoming a developer. I agree that ANSI SQL is a good standard and that it is nice that you can change platforms easily to Oracle or Sybase without having to learn SQL over again. I disagree, however, with you on the Powershell front. I really think that PowerShell is the best thing that MS has done in years. Think about it, One, in my opinion, intuitive, easy to learn, language that can not only do server administration but also sql server, exchange, and many more to come now that PowerShell support is a Common Engineering Requirement for MS Products in 2009. Powershell lets you do so much I just do not understand not wanting to learn it. I have a Windows Administration Background and have been moved into DBA work in the last year. I work with Sybase, Oracle, and MSSQL Server. I will be changing roles and working more exclusively with MSSQL in the future but I still think PowerShell is the future for administering any MS Enterprise level product. just my two cents. Good blog and I am glad that I found it from Denny Cherry's link. I agree that it is not cool to have to learn a new language all the time and that is one reason that I have never had any interest in becoming a developer. I agree that ANSI SQL is a good standard and that it is nice that you can change platforms easily to Oracle or Sybase without having to learn SQL over again. I disagree, however, with you on the Powershell front. I really think that PowerShell is the best thing that MS has done in years. Think about it, One, in my opinion, intuitive, easy to learn, language that can not only do server administration but also sql server, exchange, and many more to come now that PowerShell support is a Common Engineering Requirement for MS Products in 2009. Powershell lets you do so much I just do not understand not wanting to learn it. I have a Windows Administration Background and have been moved into DBA work in the last year. I work with Sybase, Oracle, and MSSQL Server. I will be changing roles and working more exclusively with MSSQL in the future but I still think PowerShell is the future for administering any MS Enterprise level product.

just my two cents. Good blog and I am glad that I found it from Denny Cherry’s link.

]]> By: Brian Corcoran http://www.brentozar.com/archive/2009/04/starting-the-sql-journey/comment-page-1/#comment-8515 Brian Corcoran Thu, 23 Apr 2009 15:28:21 +0000 http://www.brentozar.com/?p=3466#comment-8515 I'm 26 years old and went to school to become a Network Administrator. I was able to pick up a job as a Network Technician and soon after promoted to a Network Administrator role. Yet after 4 years here, I find myself less and less interested in networking and windows administering, and more and more fascinated with the database role. Right out of school, the concept of a database was completely foreign to me. It's not that I didn't know about them, I just had no idea how they worked. Now, as my role here as grown more into the reporting needs for our company, and I've gotten the chance to work with the couple different databases we have, I've really started to become obsessed with it. Several weeks ago I started researching what I needed to do to become a DBA, which has lead me to this site and several others that have been really helpful. And now after reading how you've become a DBA, it's even more inspiration to do the same. So I just wanted to say thanks! I’m 26 years old and went to school to become a Network Administrator. I was able to pick up a job as a Network Technician and soon after promoted to a Network Administrator role. Yet after 4 years here, I find myself less and less interested in networking and windows administering, and more and more fascinated with the database role. Right out of school, the concept of a database was completely foreign to me. It’s not that I didn’t know about them, I just had no idea how they worked.

Now, as my role here as grown more into the reporting needs for our company, and I’ve gotten the chance to work with the couple different databases we have, I’ve really started to become obsessed with it. Several weeks ago I started researching what I needed to do to become a DBA, which has lead me to this site and several others that have been really helpful.

And now after reading how you’ve become a DBA, it’s even more inspiration to do the same.

So I just wanted to say thanks!

]]> By: Tim Edwards http://www.brentozar.com/archive/2009/04/starting-the-sql-journey/comment-page-1/#comment-8490 Tim Edwards Wed, 22 Apr 2009 15:25:47 +0000 http://www.brentozar.com/?p=3466#comment-8490 This is always an interesting topic. I always find it fascinating to find out how my colleagues got to where they are at because it seems like, in this occupation, there is such a variety of paths people have taken to get here. I, myself, came into databases through a financial background. I started my career almost 20 years ago as a CPA and internal auditor and quickly was thrown into EDP auditing. I was fascinated with computers from my exposure through auditing and tried to automate my job as an auditor as much as I could through the use of electronic workpapers and schedules, DBASE IV code and Microsoft Access code to look for patterns, etc. All of this took me from auditing to Microsoft FoxPro development, which quickly turned into SQL Server development when the databases and number of users became too large and great. I have been a fulltime DBA for about 12 years now and consider myself more of an administrative DBA (manage for uptime, performance, etc) versus some of my peers who are great database developers or architects. Thanks BrentO and SQLChicken for this topic. I look forward reading how others came into the SQL Server world. This is always an interesting topic. I always find it fascinating to find out how my colleagues got to where they are at because it seems like, in this occupation, there is such a variety of paths people have taken to get here. I, myself, came into databases through a financial background. I started my career almost 20 years ago as a CPA and internal auditor and quickly was thrown into EDP auditing. I was fascinated with computers from my exposure through auditing and tried to automate my job as an auditor as much as I could through the use of electronic workpapers and schedules, DBASE IV code and Microsoft Access code to look for patterns, etc. All of this took me from auditing to Microsoft FoxPro development, which quickly turned into SQL Server development when the databases and number of users became too large and great. I have been a fulltime DBA for about 12 years now and consider myself more of an administrative DBA (manage for uptime, performance, etc) versus some of my peers who are great database developers or architects.

Thanks BrentO and SQLChicken for this topic. I look forward reading how others came into the SQL Server world.

]]>