Why its important to read MSDN documents carefully....
-
I was reading through this article[^] and decided to lookup NEWSEQUENTIALID in MSDN to read about it. I tell you, Microsoft makes a pretty bold statement: "Creates a GUID that is greater than any GUID previously generated by this function on a specified computer since Windows was started." And then, for those who are concerned about identity theft or an invasion of privacy, Microsoft says: "If privacy is a concern, do not use this function."
Actually that all makes perfect sense: It's useful because sequentially greater GUID's are extremely useful for performance in SQL server since you can create a clustered index by them for huge performance gains if you use Guid's as your primary key for your tables. They are a security risk only in that you can tell something about the underlying data such as guessing what the next ID might be if you know a given ID which I wouldn't consider a particularly huge risk but there is one depending on how secure you write the rest of the code.
"Creating your own blog is about as easy as creating your own urine, and you're about as likely to find someone else interested in it." -- Lore Sjöberg
-
Actually that all makes perfect sense: It's useful because sequentially greater GUID's are extremely useful for performance in SQL server since you can create a clustered index by them for huge performance gains if you use Guid's as your primary key for your tables. They are a security risk only in that you can tell something about the underlying data such as guessing what the next ID might be if you know a given ID which I wouldn't consider a particularly huge risk but there is one depending on how secure you write the rest of the code.
"Creating your own blog is about as easy as creating your own urine, and you're about as likely to find someone else interested in it." -- Lore Sjöberg
There is also the issue of the GUID containing the MAC Address of the PC generating it.
-
There is also the issue of the GUID containing the MAC Address of the PC generating it.
-
There is also the issue of the GUID containing the MAC Address of the PC generating it.
That is ancient. Since Windows 2000 Guids are not based on Mac Address.
-
Actually that all makes perfect sense: It's useful because sequentially greater GUID's are extremely useful for performance in SQL server since you can create a clustered index by them for huge performance gains if you use Guid's as your primary key for your tables. They are a security risk only in that you can tell something about the underlying data such as guessing what the next ID might be if you know a given ID which I wouldn't consider a particularly huge risk but there is one depending on how secure you write the rest of the code.
"Creating your own blog is about as easy as creating your own urine, and you're about as likely to find someone else interested in it." -- Lore Sjöberg
I guess I'm the only one who read it in a literal sense and laughed... :doh:
-
I guess I'm the only one who read it in a literal sense and laughed... :doh:
No, I laughed too.... "Creates a GUID that is greater than any GUID previously generated by this function..." I almost expect to see Billy Mays (R.I.P.) pitching it... :) "The greatest GUID ever!"
WE ARE DYSLEXIC OF BORG. Refutance is systile. Your a$$ will be laminated. There are 10 kinds of people in the world: People who know binary and people who don't.
-
I was reading through this article[^] and decided to lookup NEWSEQUENTIALID in MSDN to read about it. I tell you, Microsoft makes a pretty bold statement: "Creates a GUID that is greater than any GUID previously generated by this function on a specified computer since Windows was started." And then, for those who are concerned about identity theft or an invasion of privacy, Microsoft says: "If privacy is a concern, do not use this function."
The algorithm for sequential ID's has some advantages in some scenarios (as another reply descibes). Furthermore, it does not hash and thus the MAC address of the machine generating the GUID is clearly visible. IIRC a high profile worm author / spammer / scammer was actually identified by a GUID automatically embedded in some (word?) document. So yeah, the privacy concern is real :)
Personally, I love the idea that Raymond spends his nights posting bad regexs to mailing lists under the pseudonym of Jane Smith. He'd be like a super hero, only more nerdy and less useful. [Trevel]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server -
I guess I'm the only one who read it in a literal sense and laughed... :doh:
"Creates a GUID that is greater than any GUID previously generated by this function on a specified computer since Windows was started" Yeah, guess it creates GUID's that are greater than any GUID created since the 80's or 90's (whenever "Windows was started"). :laugh:
Visual Studio is an excellent GUIIDE.
-
I was reading through this article[^] and decided to lookup NEWSEQUENTIALID in MSDN to read about it. I tell you, Microsoft makes a pretty bold statement: "Creates a GUID that is greater than any GUID previously generated by this function on a specified computer since Windows was started." And then, for those who are concerned about identity theft or an invasion of privacy, Microsoft says: "If privacy is a concern, do not use this function."
I've read some plain wrong statements, and seen some worst possible code samples. But unfortunate as it could be, that's all the option we have.
“Follow your bliss.” – Joseph Campbell
-
I stopped relying on MSDN since they started letting boneheads author the content.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane
Hehehe. And in addition to that; it's pretty much impossible finding anything on MSDN without using Google. And even then most links you find in forums discussing what you googled for are dead since the content has moved for the umpfteenth time that year. And the MSDN teams response? Change the color of the graphics in MSDN from red to blue... :~
If I cannot find a way I will make one
-
Actually that all makes perfect sense: It's useful because sequentially greater GUID's are extremely useful for performance in SQL server since you can create a clustered index by them for huge performance gains if you use Guid's as your primary key for your tables. They are a security risk only in that you can tell something about the underlying data such as guessing what the next ID might be if you know a given ID which I wouldn't consider a particularly huge risk but there is one depending on how secure you write the rest of the code.
"Creating your own blog is about as easy as creating your own urine, and you're about as likely to find someone else interested in it." -- Lore Sjöberg
-
"Creates a GUID that is greater than any GUID previously generated by this function on a specified computer since Windows was started" Yeah, guess it creates GUID's that are greater than any GUID created since the 80's or 90's (whenever "Windows was started"). :laugh:
Visual Studio is an excellent GUIIDE.