If I only know TSQL can I call myself programmer?

Question

I am dealing with MS SQL since from version 2000 even before that, I think that I am pretty good in writing TSQLs and general database designs . Can I consider myself as programer ?
I know that TSQL is not enough for any kind of application so i started learning C# but I looks like that is much longer way then mastering TSQL and SQL server.

Answer 1

I am going to assume you've written stored procedures, functions, etc to support various databases/schemas.

Yes, you can say you are a programmer. However I would probably caveat it and say you are a DB programmer. In my experience when people ask if someone is a programmer they seem to normally be asking if you are a application/web programmer.

I can understand your statement about C# taking a while to pickup. I am helping to convert some DB programmers to application programmers and they are going through a learning pain as well. Things that application developers take for granted the DB developers generally haven't had to think about (reference vs. value types, etc.).

Answer 2

TSQL is mostly a declarative programming language (with some other stuff like UDTs, UDFs, SPs, cursors, etc.), so I guess strictly speaking you could say that you are a programmer. In reality though: no, I would say that T-SQL by itself is not what most people think a programmer is.

Answer 3

You can call yourself anything you would like, even if it isn't true. In this case, if you can complete almost any database programming task in T-SQL you can call yourself a programmer and it would be a true statement. (Some C programmers may disagree.)

Answer 4

T-SQL is code, it is a programming language: what more do you need?

Although, if are re-designing and tuning the work of other programmers T-SQL efforts to make it work then perhaps you're a developer.

I'm a Developer DBA who knows a little of C# and other languages. The label doesn't worry me...

Answer 5

That depends: have you done any programming?

If all you've done is designed databases and created queries, no.

If you regularly write complex stored procedures, then maybe.

If you've only done a little bit of programming, that doesn't make you a Programmer, unless it is one of your key roles.

Answer 6

If you are writing stored procedures and so processing data in the DB tables with logic then I would call you a programmer.

You might want to say you are a DB programmer or a procedural programmer so as not to be confused with an object oriented programmer but programming in my mind is simply processing data with first order logic.

Regarding C# you need to get your head around object orientating programmer to master it which is very different to database programmer but I would say C# is a great language to get up to speed with Objects in. Good luck!

Answer 7

Yes

Database programming is extremely important.

Answer 8

You are definitely a programmer, but typically someone with your skill set is called a DBA or Database Administrator. It is just as important as application programming in many types of environments, but is quite different. Keep in mind, I would typically expect a DBA I was hiring as a DBA to be an extremely advanced SQL user, otherwise I would probably just hire an application developer who is probably going to be an intermediate SQL user anyway (not all, but most are).

I would say you could go either way at this point; become a SQL guru who can come in an optimize a wacky database configuration with his hands tied behind his back, or become an application developer with a very strong SQL background. Either CVs are quite desirable.

Answer 9

Here is the simplest possible definition of a programmer, paraphrased from Stephen King: if you wrote code and it worked, and you were paid for it, and when you cashed the check it didn't bounce, then yes, you are a programmer. :)