Kevin, I don't know if you've done much/any computer programming type work in your life, but if not, here are a couple of somewhat random thoughts about CS and the workplace:
I started doing computer programming work when I was about 10. I got my first programming job when I was 15, granted this was through a family hookup, but it was real work and EXCELLENT experience. When I got out of high school, I went to Texas Tech and got a CS degree. After college, I had a hard time finding a good job in the metroplex without moving to Richardson/Plano area, something I would NOT consider. I've been pretty lucky, I'm able to keep up a small business doing consulting programming for some small to medium sized insurance marketing companies. I've found kind of a niche in thier business, particularly comissions, which makes previous experience in life doing work on a payroll system handy.
I don't know where you'd go for your actual CS coursework, but at TTU, it's kind of like an engineering degree: They teach you theory of things, but they AREN'T really teaching you to go out and do software work, database admin, etc. Also, I only had to take one extra math class to get a minor, so you can plan on seeing a lot more math geeks before you're done

Calc I and Calc II are kind of the bust-out classes, once you get past those it doesn't necessarily get easier, but the passing rates are a lot better.
I was fortunate that I already had a lot of REAL programming experience when I graduated from college, because when the opportuinity I had to get into what I do now came along, without that experience, I never would have been able to hack it. In my opinion, it takes someone 2-4 years to get really good at being a developer, and if you look at job postings, this is kind of what you see, everybody wants to hire people with 4 years of experience, and those jobs pay too. Similar, maybe not quite as long a curve, for database admin. So, what's the point? If you can, and I'm sure it would be tough, because you've got a lot on your plate, start working on what you want to do for a career NOW, while you're still in school. Personally, I mostly build SQL Server/.NET systems with ASP.NET web interfaces. They probably won't teach you anything at all about these technologies in a CS program. But, you can start reading books, get the stuff (you should be able to get student pricing on most of this stuff) and start working on it on your own. When you're comfortable, try to find some real work: The jump from playing with programming/database stuff on your own computer on projects you dreamed up to real world professional apps/databases is a HUGE jump. However, if you can make that jump while you're still in school, you've got a HUGE advantage in the job market when you graduate.
Couple this with the right attitude and communication skills, and you can be a real hot commodity. Granted, I'm working for smaller business, but the most important skill I think I have is the ability to sit down with somebody who has no idea what kind of computer system they need and understand what to do asking them questions.
The only other thought I'd share here, which you've probably heard before, is that this type of work tends to induce burnout in a lot of people, hell, probably anybody with a personality. I don't know how avoid it or anything like that, but it's a consideration.
I hope some of this helps, good luck with your decision!