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......


Moderator: dromia
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......
![]()
the NRA run SQL Server on the presumed SBS server that runs the rest of the business.
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
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.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.
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.christel wrote: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.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.
Users browsing this forum: No registered users and 16 guests