sql server connection string cheat sheet

Stores a result set for later processing. You can store xml instances in a column or a variable.

Stores a globally unique identifier (GUID). Stores a database-wide unique number that gets updated every time a row gets updated.

Stores values of various SQL Server-supported data types, except text, ntext, and timestamp. Prefer to use the varbinary(max) type as the image type will be removed in future versions. Is a datetime2 datatype with the UTC offset appended. Presicion 1-2 = 8 bytes precision 3-4 = 9 bytes precision 5-7 = 10 bytes The precision logic is the same as for the time datatype. Presicion 1-2 = 6 bytes precision 3-4 = 7 bytes precision 5-7 = 8 bytesĬombines the date datatype and the time datatype into one. Casting values to a lower precision will round the value. TIME(7) is the highest and the default precision. TIME(3) will have milliseconds precision. If you are running SQL Server 2008 or later and need milliseconds precision, use datetime2(3) instead to save 1 byte. For both the minimum is 1 and the maximum is 38.Ĥ bytes when precision is less than 25 and 8 bytes when precision is 25 through 53 The Decimal and the Numeric data type is exactly the same. Precision 1-9 = 5 bytes, precision 10-19 = 9 bytes, precision 20-28 = 13 bytes, precision 29-38 = 17 bytes The columns named 8, 9, 10 and 11 indicates SQL Server version data type support whereġ to 8 bit columns in the same table requires a total of 1 byte, 9 to 16 bits = 2 bytes, etc. Once learned the sql data types available and spending a few extra minutes when designing your schema will result in faster query execution and an overall better performing database.

This will make the whole server perform better as there will be more resources available for other things. So, queries will perform faster, release locks earlier (if any) and use less system resources (memory and CPU). That's not much in terms of disc space ('storage is cheap, etc') but you'll probably have indexes containing that column and if that index takes less memory the database engine will process that index much more efficient in every 'join' and 'where' etc. With 100,000 records you will save 300,000 bytes. Choosing the sql data type tinyint instead of int for a 'ProductType' column with values ranging from 1 to 10 will save three bytes per record.

Sql server connection string cheat sheet