Tuesday, July 14, 2009

An SQL Server Administrator needs to know programming or not?

Beside writing T-SQL queries does a SQL Server 2005 Administrator needs to know programming?





I was wondering if a SQL Server 2005 Administrator or Developer needs to have a deep knowledge in C# or other NET languages?? I mea n is it required? I was under the impression that SQL %26amp; T-SQL programming and SQL Administratives tasks were the only requirement to apply for a sql server job??





Thanks.

An SQL Server Administrator needs to know programming or not?
Yes, indeed. If you want a certification, it's part of the requirements.


TSQL queries are not enough, you might need to create stored procedures, views or triggers which are a common use of TSQL in a programmatic way. Queries are not the only way to handle data as well, sooner or later you'll have to deal with cursors too. Even jobs might call a SP or have some code to perform some task. You can use ActiveX from TSQL and that requires to connect to an ActiveX DLL and use its methods and properties, usually this is wrapped in a SP.


If you use SQL 2005 then you need also to know any .NET language to create stored procedures, views or triggers that might require more powerful calculations. If you need a lot of number crunching or low level access then you might even need to create an extended stored procedure in C++, but this mostly for extreme performance cases such as scientific, financial, etc...
Reply:yes it is required. You must atleast know how to make the sql queries through C#, J# or most applications. As an administrator the most problem faced are glitch in programming, they cause trouble, and in order to troubleshoot ( debug ), you must know at least the language that was used to create the application you are using binded with SQL.





Just knowing SQL is never enough, when a problem occurs like the application says " unable to make queries " , you need to get to the root of the application to find the glitch, the problem might be as simple such as a Wrong time stamp or overload...


No comments:

Post a Comment