Actually, the goverment knows who is gets access. You forget physical coutermeasures on a closed and encrypted network. NT works fine for a secure system in this situation.
Open Source is fine, but maybe the facility does not have the money to sit and wait for the internet to go through all the code required for a nuclear material inventory system and offer their perfect solution.
Bug in the programming.... and yep MS said you have a bug in your programming.
Why were they involved? Because some mangler got his hands on a report from a tech who was smart enough to find the bug, but not quiet good enough to understand that if you can write SQL different ways and get different returns and its not a Database problem. So this tech tells the mangler that the database has a problem. The mangler sends it to MS and it leaks out about the "problem" then you get 100s of people bashing MS and some idiot who writes an article about software not even in use anymore.
In a word, duh... However, Los Alamos (and a good deal of the military) doesn't *use* Microsoft products, except in the case of laptops, etc, non mission critical machines... Half of them are using Unix or whatnot, OS's that have been time tested as reliable and suited to mission critical applications...
Wrong, actually many use C2 Locked down Windows NT servers on encrypted networks. These systems are mission critical.
Actually, its a code problem. Bottom line, in SQL Server you dont use a do loop while using the same variable in the select statement that you use in the where clause. Instead you should use a courser and feed an independent variable to use in the where clause. Syntax wise both will work (on any ANSI standard DBMS) but each will return different result sets.
Now since your using the incorrect select statement to return records... you get incorrect updates in your journal tables. Thus "records disappear".
Slashdot Mirror
Actually, the goverment knows who is gets access. You forget physical coutermeasures on a closed and encrypted network. NT works fine for a secure system in this situation. Open Source is fine, but maybe the facility does not have the money to sit and wait for the internet to go through all the code required for a nuclear material inventory system and offer their perfect solution.
Bug in the programming.... and yep MS said you have a bug in your programming. Why were they involved? Because some mangler got his hands on a report from a tech who was smart enough to find the bug, but not quiet good enough to understand that if you can write SQL different ways and get different returns and its not a Database problem. So this tech tells the mangler that the database has a problem. The mangler sends it to MS and it leaks out about the "problem" then you get 100s of people bashing MS and some idiot who writes an article about software not even in use anymore.
In a word, duh... However, Los Alamos (and a good deal of the military) doesn't *use* Microsoft products, except in the case of laptops, etc, non mission critical machines... Half of them are using Unix or whatnot, OS's that have been time tested as reliable and suited to mission critical applications... Wrong, actually many use C2 Locked down Windows NT servers on encrypted networks. These systems are mission critical.
Actually, its a code problem. Bottom line, in SQL Server you dont use a do loop while using the same variable in the select statement that you use in the where clause. Instead you should use a courser and feed an independent variable to use in the where clause. Syntax wise both will work (on any ANSI standard DBMS) but each will return different result sets. Now since your using the incorrect select statement to return records... you get incorrect updates in your journal tables. Thus "records disappear".