I love the abuse levelled before you actually know what the app is.
It's an old VBA GIS application linking to an Oracle Spatial DB holding maps. The data gets locked by the application and if the users haven't logged out, it stays locked and cannot be updated. I guess I should have been more specific but it was a vent, nothing more...
Oh, and for all the sledging, you obviously realise that having more than one person at a time edit spatial data is a big no no...
- Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
- Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
- You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
- You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
- If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Logging in...
Previously on "Should DBA know to check theres no DB connections before performing a data update"
Collapse
-
Originally posted by aussielong View PostYour architectures dont use optimistic locking then? Are you not using versioning on your rows? Which you usually should be in scalable multiuser systems.
The DBA update would incr the version number. The cache would not be able to overwrite that later. You should handle optimistic locking version error in your app-reload the latest version and maybe try again. This is how I've used ORMs such as Hibernate in the past. It's a standard approach.
Bouncing the DB should be an absolute last resort due to needing to refill caches in the middle tier.
Leave a comment:
-
Originally posted by minestrone View PostIf you are using ORM which mostly everyone does these days in writing java apps ( I would think .NET has eventually got there as well) and using third level caching which you should be then you have to drop the appication or else what you are updating might be written over by the application cache.
It is pretty standard tech and a pretty standard way of using it.
As I said it depends on the use of the DB but it is normal ( necessary )to drop the connections on the architectures I use.
The DBA update would incr the version number. The cache would not be able to overwrite that later. You should handle optimistic locking version error in your app-reload the latest version and maybe try again. This is how I've used ORMs such as Hibernate in the past. It's a standard approach.
Bouncing the DB should be an absolute last resort due to needing to refill caches in the middle tier.Last edited by aussielong; 6 January 2013, 23:15.
Leave a comment:
-
ORMs are terribly misunderstood by most people that use them, fantastic at delivering clean code quickly written to do page sized data loading but I keep finding people writing batch jobs with it. Battering the shit: out of the DB for minutes on end to do something a stored proc could do in a second.
Leave a comment:
-
Originally posted by minestrone View PostIf you are using ORM which mostly everyone does these days in writing java apps ( I would think .NET has eventually got there as well) and using third level caching which you should be then you have to drop the appication or else what you are updating might be written over by the application cache.
It is pretty standard tech and a pretty standard way of using it.
As I said it depends on the use of the DB but it is normal ( necessary )to drop the connections on the architectures I use.
Leave a comment:
-
Originally posted by centurian View PostSounds like the application architecture needs a rethink.
It is pretty standard tech and a pretty standard way of using it.
As I said it depends on the use of the DB but it is normal ( necessary )to drop the connections on the architectures I use.Last edited by minestrone; 6 January 2013, 17:57.
Leave a comment:
-
Originally posted by Kanye View PostSorry OP but I'm approaching 10 years as a DBA/developer, mostly direct for Oracle, and have never once had a scenario where people have had to log out for a 'data update'.
Now I have had a few applications where this might have been an issue, so the application / DB schema accomodated this, by being able to pre-load the data gradually, but in an inactive state - and then made active when ready.
Sounds like the application architecture needs a rethink.
Leave a comment:
-
Sorry OP but I'm approaching 10 years as a DBA/developer, mostly direct for Oracle, and have never once had a scenario where people have had to log out for a 'data update'.
Occasionally some DDL or huge table level updates are scheduled for outside of business hours, but even then, leaving the occasional session connected should not be the end of the world.
Sounds like a flaw in the application locking or change processes rather than with the DBA.
Leave a comment:
-
-
Personally, I code all my apps to check a database table every 90 seconds which has an entry for each program name and a true or false. If true the program gracefully closes, and then refuses to start up until its back to false.
This way I can close systems down quickly, safely and no one "forgets" and goes for lunch with their screen locked and the program still running. Before I started doing this it was easy to spend 30 mins ringing around, then walking around logging people out of apps. Often after 20 mins the people who had already come out would think it was done and go back in.
But as others have said with SQL you can do an awful lot with people still using the database.
Leave a comment:
-
Originally posted by Old Hack View PostWell I had assumed the down was planned and emails sent, and that any checks would be cursory, but he didn't kick anyone off, just did the update.
Like the last bit...
All the time know that you had to take this advice from Suity
Leave a comment:
-
Originally posted by Old Hack View PostSorry, 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 ****.
HTH BISDI
Leave a comment:
-
If it is a SQL Server (Microsoft) database then the only time you need to kick out all the users is if you are restoring a database from a backup. With one exception in all other situations you can make any changes you like, including dropping and re-creating tables, and users logged on won't affect that.
The one exception is if logged on users have open transactions holding locks on database objects - that will prevent changes to anything thus locked. But it is bad application design for a client to hold locks for an extended period of time.
Leave a comment:
- Home
- News & Features
- First Timers
- IR35 / S660 / BN66
- Employee Benefit Trusts
- Agency Workers Regulations
- MSC Legislation
- Limited Companies
- Dividends
- Umbrella Company
- VAT / Flat Rate VAT
- Job News & Guides
- Money News & Guides
- Guide to Contracts
- Successful Contracting
- Contracting Overseas
- Contractor Calculators
- MVL
- Contractor Expenses
Advertisers
Contractor Services
CUK News
- Streamline Your Retirement with iSIPP: A Solution for Contractor Pensions Sep 1 09:13
- Making the most of pension lump sums: overview for contractors Sep 1 08:36
- Umbrella company tribunal cases are opening up; are your wages subject to unlawful deductions, too? Aug 31 08:38
- Contractors, relabelling 'labour' as 'services' to appear 'fully contracted out' won't dupe IR35 inspectors Aug 31 08:30
- How often does HMRC check tax returns? Aug 30 08:27
- Work-life balance as an IT contractor: 5 top tips from a tech recruiter Aug 30 08:20
- Autumn Statement 2023 tipped to prioritise mental health, in a boost for UK workplaces Aug 29 08:33
- Final reminder for contractors to respond to the umbrella consultation (closing today) Aug 29 08:09
- Top 5 most in demand cyber security contract roles Aug 25 08:38
- Changes to the right to request flexible working are incoming, but how will contractors be affected? Aug 24 08:25
Leave a comment: