concept default in category sql

This is an excerpt from Manning's book SQL Server MVP Deep Dives Vol. 2.
So the primary key is an arbitrary selection! Or is it? Although logically any of the candidate keys can be used to identify the row, a primary key must shoulder several other responsibilities besides unique identification. These include most often serving as the parent node in foreign key relationships, being used by default as the clustering key for the table’s physical index structure, and not allowing NULL values. In this chapter, I’ll use the following highly simplified definitions of the various types of keys:
Listing 4. The Parse() function
public static Complex Parse(SqlString s) { if (s.IsNull) return Null; Complex u = new Complex(); // Put your code here string tmp = s.ToString().Trim(); // Evaluate imaginary part (if there is one) first if (tmp.EndsWith("i")) { // Find last - or + sign char[] MinusOrPlus = new char[2] { '-', '+' }; int Last = tmp.LastIndexOfAny(MinusOrPlus); // No + or - is not an error; "17.3i" is a valid complex number. // Change -1 to 0 to prevent error in substring expression. if (Last < 0) { Last = 0; } string imag_str = tmp.Substring(Last, tmp.Length - Last - 1).Trim(); switch (imag_str) { case "": case "+": u.m_imag = 1; // Special case handling for "i" / "+i" break; case "-": u.m_imag = -1; // Special case handling for "-i" break; default: try { u.m_imag = double.Parse(imag_str, CultureInfo.InvariantCulture); } catch (Exception ex) { throw new ArgumentException( "Error converting imaginary part (" + imag_str + "i): " + ex.Message); } break; } // Strip off the imaginary part, to leave just the real part // Note special case handling for complex numbers with no real part tmp = (Last == 0 ? "0" : tmp.Substring(0, Last).Trim()); } // tmp now contains only the real part; use Double.Parse() try { u.m_real = double.Parse(tmp, CultureInfo.InvariantCulture); } catch (Exception ex) { throw new ArgumentException("Error converting real part ( " + tmp + "): " + ex.Message); } return u; }
2. On the next screens, choose the defaults until you see the second Setup Support Rules page, where you should click Install. Validate that the checks return successful results. If the checks returned a few warnings, make sure you fix them before proceeding with the installation. Click Next.

This is an excerpt from Manning's book SQL Server MVP Deep Dives.
All of this leads us to a database setting called READ_COMMITTED_SNAPSHOT that will change the way the default READ COMMITTED isolation behaves. This setting uses SNAPSHOT isolation level at a statement level, so the results you get for a query will only include rows that have been committed; but if someone changes the data after you start getting results, you won’t see that. This is generally good enough locking, and it is certainly enough if you are using optimistic locking techniques to protect users from overwriting other users’ changes.
Integrated Security—The security mode to use. This setting determines whether ADO.NET uses trusted (SSPI) Windows authentication or untrusted SQL Server authentication. In the latter case, this includes a specific Login Name and matching password. The default is False. See the section “Trusted or untrusted security?” later in this chapter.