August 17, 2005 at 7:15 am
It would seem sensible to learn at least one additional language to T-SQL. If I had to choose one, what would you experts recommend and why? VBscript, Perl, etc?
I am supporting SQL 6.5,7 and 2000 with no immedaite plans to move to 2005.
August 17, 2005 at 9:48 am
OK, I'll bite. Learn one of the .NET languages, VB.NET or C#. They are fun, and useful, and capable. 🙂
August 17, 2005 at 2:36 pm
I agree, learning C# is definitely not wrong for the future. SQL Server 2005 brings CLR Integration, but you said that you have no immediate plans to upgrade. Still, it is always good to know a little about the 'outside environment' even if you are a DBA, and that environment is becoming more and more .NET code.
If you are a specialized production DBA in a shop with others that are more developer oriented you might want to pursue Perl though. It is a great language for automating some typical DBA tasks such as reviewing logs etc.
August 19, 2005 at 5:54 am
I agree with Chris Hedgate. If you are mainly a Windows shop then one of the .Net languages should be your first priority. C# would be my choice, unless your place is 100% VB.
If you are likely to work with non-Windows databases, then Perl is a good choice, as many *nix people use this as their preferred scripting language.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply