The DBA in a large shop won't always have to program, but will definitely need to be responsive to programmers. It will be very difficult for you to help programmers do their work if you don't understand the minimum about what they're doing.
If you're using MS SQL server, it's most likely you're talking about a MS shop. This means the programmers will likely be using C# and VB.NET. You should have a basic understanding of these languages, how the work with data, and their inherent strengths and weaknesses.
If you're in a smaller shop, the DBA often is also a programmer. In this case you'll definitely need formal programming languages.
I'm not sure I know what you mean by "sticking with the administration part." If you're creating and maintaining data design, normalizing the data, and managing the data queries, updates, backups, joins, and back-end logic, you're half-way to programming already.
Another note. One of the other respondents referred to SQL Server as SQL. This is not technically correct and very misleading. SQL is the (mostly) universal language of databases. SQL Server is Microsoft's proprietary database server environment.
It's absolutely critical that you learn generic SQL if you want to be a data administrator. The actual environment (SQL Server, Oracle, MySQL) is important too, but as an implementation of the SQL.
To return to your original question, it's never a bad career move to know some programming. If you've already got a data job , you'll be better at it if you can see the programmer's perspective. If you don't currently have this type of employment, a combination DBA / Programmer is far more valuable than somebody with only one skill or the other.