Should DBA know to check theres no DB connections before performing a data update

[Old Hack]

Old Hack is correct. The DBA should have dropped all of the users first without telling them & then run the update.

It's Spatial data, it cannot be accessed and updated at the same time. The minimum I would have expected would have been to have pencilled in down time, to have bounced the spatial database at downtime, to ensure those that forgot the downtime weren't on, the upload to proceed, with applications servers also being down, then the upload being completed, then all started again.

As the application only serves the spatial data that is being updated, I don't see why they didn't consider it.

[stek]

Should DBA know to check theres no DB connections before performing a data update

Old Hack is correct. The DBA should have dropped all of the users first without telling them & then run the update.

That'll delete em won't it? Or put them in recycle bin if its Oracle

Or was that sarcasm?

[doodab]

It's Spatial data, it cannot be accessed and updated at the same time. The minimum I would have expected would have been to have pencilled in down time, to have bounced the spatial database at downtime, to ensure those that forgot the downtime weren't on, the upload to proceed, with applications servers also being down, then the upload being completed, then all started again.

As the application only serves the spatial data that is being updated, I don't see why they didn't consider it.

Are they responsible for the application or are they just the DBAs?

[adubya]

A decent deployment guide should specify all the steps to perform, including any checks required before actioning the deployment.

Our deployments are carried out by a separate team (to dev) and so the guides need to be comprehensive and robust.

[suityou01]

A decent deployment guide should specify all the steps to perform, including any checks required before actioning the deployment.

Our deployments are carried out by a separate team (to dev) and so the guides need to be comprehensive and robust.

This sounds more like it. Who signs off the deployment docs OH? Where's your governance?

Sounds like you just chucked a doc at a dba.

[NickFitz]

Old Hack is correct. The DBA should have dropped all of the users first without telling them & then gone home early because it's Friday, leaving the system offline for the whole weekend.

FTFY

[Old Hack]

Sorry guys, but, imo, if a DBA knows about loading data, which they should, they should know to make sure no one is accessing the data when loading it.

I came on to vent, but a lot of the responses seem at odds as to how I have ever operated, and all IT folk from the clients whom pay me.

I expected MF to get it wrong, for he owned clothes shops, is developing end terraces and bought too many sleds....

[suityou01]

Sorry guys, but, imo, if a DBA knows about loading data, which they should, they should know to make sure no one is accessing the data when loading it.

I came on to vent, but a lot of the responses seem at odds as to how I have ever operated, and all IT folk from the clients whom pay me.

I expected MF to get it wrong, for he owned clothes shops, is developing end terraces and bought too many sleds....

So if you wanted live updates and DIDN'T want the end users chucked out, how would you let the DBA know?

[Old Hack]

So if you wanted live updates and DIDN'T want the end users chucked out, how would you let the DBA know?

Sorry, this is an application which serves map data; the only thing they can update is the map data, and it cannot be updated whilst users are on it. That's a known part of the system.

Jesus, no wonder everyone thinks you're a ****.

[OwlHoot]

Surely a DBA has to understand that if he is performing a data update, he can't have users in the system? So surely, he has to check no one is connected, before updating business data?

No, assuming the DBA emailed everyone to announce the forthcoming upgrade, there's no need to check only to chuck, i.e. everyone off when it starts

and if any users lose a load of critical irreplaceable data, so much the better, as it means next time they'll take more notice of the DBA's emails.