The UK's Finest Independent Forum for Shooters and Gun Owners. Est 2010.

NRA Armoury theft -
The NRA today admitted that unfortunately they had lost another 5 firearms whilst the IT specialists continued to argue about the merits or otherwise of SQL variants. A spokesman commented that it should be viewed as a sequel......

desperatedan wrote:NRA Armoury theft -
The NRA today admitted that unfortunately they had lost another 5 firearms whilst the IT specialists continued to argue about the merits or otherwise of SQL variants. A spokesman commented that it should be viewed as a sequel......

You two do realise that SBS doesn't exist anymore, right? And MS Server Essentials 2012 doesn't come with SQL either...

*just sayin'*

Yeh 2011 was the last release, but in the example above, they already had it...

the NRA run SQL Server on the presumed SBS server that runs the rest of the business.

How many programmers does it take to change a light bulb?







10






1 to change the bulb and








9 to say they could have done it better

knewmans wrote:How many programmers does it take to change a light bulb?







10






1 to change the bulb and








9 to say they could have done it better

TattooedGun wrote:If this were my company providing the solution, making the same assumption as Mr Logic, we'd probably suggest that the NRA run SQL Server on the presumed SBS server that runs the rest of the business. However, it's a big assumption to make.

If it was my company providing a solution I would focus on best practice and firearms storage procedures with robust independent audit systems and strict control of access to the environment. We use a token system here so any access at any time is recorded by the system as an event. I would also be looking at a bag and tag system so the person lodging the firearm is responsible for securing it within something such as a protective sock which is then security sealed. If the firearm/item when collected has a broken or damaged seal there needs to be a very good reason for it. Any database used would be purely to log the date and recipient, the item owner, description, location with in the armoury and finally who checks it back out again. It would go a long way towards safeguarding both the armoury staff and the owner from potential claims.

Would be interested to hear more about your token system....

christel wrote:

TattooedGun wrote:If this were my company providing the solution, making the same assumption as Mr Logic, we'd probably suggest that the NRA run SQL Server on the presumed SBS server that runs the rest of the business. However, it's a big assumption to make.

If it was my company providing a solution I would focus on best practice and firearms storage procedures with robust independent audit systems and strict control of access to the environment. We use a token system here so any access at any time is recorded by the system as an event. I would also be looking at a bag and tag system so the person lodging the firearm is responsible for securing it within something such as a protective sock which is then security sealed. If the firearm/item when collected has a broken or damaged seal there needs to be a very good reason for it. Any database used would be purely to log the date and recipient, the item owner, description, location with in the armoury and finally who checks it back out again. It would go a long way towards safeguarding both the armoury staff and the owner from potential claims.

I have no idea how the NRA armoury works, but presumably if you've got stuff in there, historically you've been able to walk in and find your rifle and take it out without too much hassle.

The trouble is if everything in the armoury is not individually lockered, then whose to stop someone who has access coming in and taking something off someone else rifle?

Sure a logging system that lets you know whose been in since it was last accounted for is fine, but all it does is narrow down the list of suspects, and even then doesnt provide conclusive proof.

The only way the Armoury should work is if it's manned, and every persons equipment is logged and photographed when it goes in and when it goes out, and only the registered user can collect the firearm, which is presented by the "armourer" which would need to be a posted position.

That way the only person who can be accountable is the armourer. if anything goes missing, it has to be those with access, who are not the end users, and they'd be for the chop.

As I say though, I don't know how it works, but from what came out it sounded like someone had access that took off items from someone else rifle... :/

Very bad news :( Not sure how a database could help unless it's photographed all accessories and such as they come in and go out. That way the NRA have proof of what was entered incase anyone was to say something went missing, but turns out it wasn't there when put in.

The inventory database itself doesn't prevent the theft it helps you determine what's been stolen. Not allowing thieves access to the armoury prevents theft.