I'm in a similar position in my company, we have multiple people from marketing and sales that have requested direct database access to do their jobs. As much as I don't like it management decrees that they must have that access.
We have created a couple of interfaces for them to use to do queries directly on the database, one web based, one XML command line based. After one of our sales people ran a query that he wrote and created a cartesian product on two 3 million row tables (It brought the MySQL server to a crawl, but not until it had run for 6 days), I started verbose logging in each of their interfaces. Every query that is run through an interface that they have SQL access to logs:
query start time
end time
rows retrieved
the query
username
hostname
This gives us a workable balance, the users get what they need and we have a direction in which to point the fingers if someone manages to take our production db again.
We also replicate to a secondary server which we direct most of our long running queries to.
"But the only reason people even use it in the first place is because it's easy. Something idiotic like this makes it a LOT less so."
I'm curious how making a phone call on the rare occasion that you need to reinstall windows makes the product a LOT less easy to use. I have 3 Windows XP systems at home and have to reinstall them once a year at most. Granted my 2 linux systems have been running for 2+ years without a reinstall.
That must be good drugs they are smoking, I can't stand waiting for dialup, I dislike the sound of the modem even more.
They must have never tried high speed. Once you go high-speed, you can never go back!
I think both products will have their places. At work I am running 3 different operating systems simultaneously so I can emulate our server environment: Windows XP Pro (as a base), Redhat 7.2 and Redhat 9. CoLinux is a really cool idea and I'll probrobly use it, but it won't help me in my work environment.
I'm in a similar position in my company, we have multiple people from marketing and sales that have requested direct database access to do their jobs. As much as I don't like it management decrees that they must have that access.
We have created a couple of interfaces for them to use to do queries directly on the database, one web based, one XML command line based. After one of our sales people ran a query that he wrote and created a cartesian product on two 3 million row tables (It brought the MySQL server to a crawl, but not until it had run for 6 days), I started verbose logging in each of their interfaces. Every query that is run through an interface that they have SQL access to logs:
query start time
end time
rows retrieved
the query
username
hostname
This gives us a workable balance, the users get what they need and we have a direction in which to point the fingers if someone manages to take our production db again.
We also replicate to a secondary server which we direct most of our long running queries to.
"But the only reason people even use it in the first place is because it's easy. Something idiotic like this makes it a LOT less so." I'm curious how making a phone call on the rare occasion that you need to reinstall windows makes the product a LOT less easy to use. I have 3 Windows XP systems at home and have to reinstall them once a year at most. Granted my 2 linux systems have been running for 2+ years without a reinstall.
Ummmm, why would they send out a promotion to 500,000 subscribers when their merchant system is already down?
That must be good drugs they are smoking, I can't stand waiting for dialup, I dislike the sound of the modem even more. They must have never tried high speed. Once you go high-speed, you can never go back!
They already track you with GPS without your permission (Cops Challenged on GPS Use), why should they stop there?
I think both products will have their places. At work I am running 3 different operating systems simultaneously so I can emulate our server environment: Windows XP Pro (as a base), Redhat 7.2 and Redhat 9. CoLinux is a really cool idea and I'll probrobly use it, but it won't help me in my work environment.