I have worked with MS SQL Server for nearly 8 years now, and although i'm not a DBA i do often work with DBAs to diagnose problems and work with them on solutions to things etc.. so, i guess for the most part i see the 'interesting' parts, the exceptions to the rule. I get a phone call whem it's something they can't do, or have not enough experience to tackle on their own.
Day to day, i would imagine it's similar to other jobs. You have the tasks that you must do every day, checking server statuses, ensuring disaster recovery plans are sufficient etc, and generally making sure things tick over so you always know where you stand in the event of disaster, and have your ass covered
The fun stuff comes in when you are involved in projects to improve system.. in my experience this is where i engage with DBAs the most. They always wade in wanting to check that any changes i or my team are making to the organisations systems will not screw with their processes etc
For me, i could do a DBA job.. i have an MCITP in SQL 2008, but DBAing does not interest me.. depending on your personality you might find it tiresome and really unless you are coming into an organisation that is a complete **** tip in terms of their system management you might not find it engaging. Only you can decide that
Oh yeah, and loads of stuff is done with T-SQL, i've never met a DBA that doesn't have their own set of special scripts to get them through the day
Shoot with any questions...