SQL Rules

[Robert Morley]

Okay, when it's shared, I've seen a few corruption issues...most especially
if someone gets "cut off" from the database while using it (i.e., power
failure, etc.), though I believe that applies regardless of splitting it.

As for testing changes against a copy of the data, I guess it depends how
complex the changes are. Certainly for the level of app I'm thinking of, I
would never even bother to test changes, I'd just make them and move on. If
I *were* doing something more complex on a relatively simple app, I'd just
do a "Copy/Paste" to the same folder, creating an "instant" backup in case
of some remarkable screw-up. I just see a split database wasting way more
time than it saves in a scenario such as I'm describing.

But hey, as you point out, ask a dozen DBA's the best way to do something,
and if you get less than a dozen different answers, you've had a good day!




Rob

 

[Brendan Reynolds]

But hey, as you point out, ask a dozen DBA's the best way to do something,
and if you get less than a dozen different answers, you've had a good day!

Well, I'm pretty sure I didn't say that. In fact, I have absolutely no idea
what response you would get if you asked a dozen DBAs anything, as I don't
think I've ever met a DBA, and certainly not a dozen of them. I kind of
assumed they were mythical beings, like the Yeti or Bigfoot!

 

[Robert Morley]

Sorry, got confused...I think it was Tom that said that earlier in the
thread. I hadn't clued in that you weren't Tom.


Rob