 drewAutomaticPremium
join:2002-07-10
Port Orchard, WA
kudos:6 | reply to SrsBsns
Re: Short sighted As a half-baked DBA, even I understand this stuff is stored *somewhere* and should be able to be removed easier than that. |
|
|
|
 badtripI heart the East BayPremium
join:2004-03-20
Albany, CA | said by drew:As a half-baked DBA, even I understand this stuff is stored *somewhere* and should be able to be removed easier than that. Believe me you be surprised how difficult even changing something "minor" could be depending on the system. Some systems were created by people who cant see past their nose. I'm sure AT&T has such a system. |
|
 SteimesI make internetsPremium
join:2002-01-08
Belle Vernon, PA
kudos:1
 ·Comcast
 ·Verizon Online DSL
| reply to drew
said by drew:As a half-baked DBA, even I understand this stuff is stored *somewhere* and should be able to be removed easier than that. I agree, I have removed much worse than codes from flat files and databases alike. Seems fishy, I would like to hear a better explanation on why this HAS to be manual.
--
Making procrastination an art form since Pluto was still a planet. |
|
 davoice
join:2000-08-12
Saxapahaw, NC
·Comporium
| AT&T's problem is it's not just in 1 system. It's in multiple places... and in a couple that aren't just big relational databases. Their mobile platform is a hodge podge of stuff inherited from: AT&T Wireless Services, Ameritech Mobile Communications, BellSouth Mobility, Southwestern Bell Mobile Systems, BellSouth Mobility DCS, BellSouth Wireless Data, Pacific Bell Wireless, Pacific Bell Wireless Northwest, SBC Wireless, SNET Mobility, and Southwestern Bell Wireless.
Remember most of those markets were TDMA conversions, so they weren't pure GSM builds. That leaves some true legacy systems in play on the back-end.
They do a decent job of making it look like 1 big system to the end customer but on the back end there are a bunch of moving pieces.
It's not insurmmountable... but w/ AT&T also being tied w/ all the SBC merger stuff, the integration guys already have their hands full. And much of the heavy lifting is outsourced. The brain trust who could have done it stateside has been steadily gutted.
We all know from Uverse that AT&T/SBC is a tightwad. In this case their tightwadism and lack of available onshore human resources directly affected a product roll-out and end-users.
}Davoice |
|
| reply to Steimes
said by Steimes:said by drew:As a half-baked DBA, even I understand this stuff is stored *somewhere* and should be able to be removed easier than that. I agree, I have removed much worse than codes from flat files and databases alike. Seems fishy, I would like to hear a better explanation on why this HAS to be manual. I third that, I have had to come up with some interesting solutions to scrape and process data. I would really doubt that they aren't using a database to store customer information. It can be done through a script or program, its just how creative they want to be. Let me tell you database or no database a little perl script with regular expressions can make that year long project turn into seconds.
Perhaps this is the reason why they need to charge $20/month for texting, $30/month for unlimited internet and another $30/month for 5GB of tethering. They need money to hire all the teens that will be clicking a button on a screen that says "MMS Enable". |
|
