Sunday, July 3, 2016
Monday, May 30, 2016
- On the computer that requires the connection string, create a new file with a file extension of .udl.
- To perform this task, you will have to be viewing file extensions. If you are unsure how to do that, seeHow To: View File Name Extensions.
- Create a new text file and then rename the three letter file extension .txt to .udl.
- For example, if you create a file named ConnectionString.txt, just rename it to ConnectionString.udl.
- The rest of these steps will assume that the file is actually named ConnectionString.udl. If you created another file name with a .udl file extension, that is fine, just substitute the appropriate name as needed in the following instructions.
- Right-click ConnectionString.udl that you just created and then click Properties.
- On the Connection tab, fill out the connection properties according to the server, authentication type, and database name that you need. This is typically something you would already know, but if you do not, you may have to contact the database administrator or go look at the database connection properties yourself. If you need help with that, check out the Server Management How To Pages .
- Click Test Connection. Hopefully it will succeed. If not, check the credentials, authentication type, and any firewalls (How to: Configure a Windows Firewall for Database Engine Access ) between servers.
- Click OK.
- Open the url file and inside you will find the connection string. For example, Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;InitialCatalog=FIMCertificateManagement;Data Source=FIMDC1 (as shown in the following figure).
- Remove Provider portion of the string. Using the example above, the connection string for the application would be: Integrated Security=SSPI;Persist Security Info=False;InitialCatalog=FIMCertificateManagement;Data Source=FIMDC1
Sunday, May 29, 2016
|(char, varchar, text)||(nchar, nvarchar, ntext)|
|Stores data in fixed or variable length||Same as non-Unicode|
|char: data is padded with blanks to fill the field size. For example, if a char(10) field contains 5 characters the system will pad it with 5 blanks||nchar: same as char|
|varchar: stores actual value and does not pad with blanks||nvarchar: same as varchar|
|requires 1 byte of storage||requires 2 bytes of storage|
|char and varchar: can store up to 8000 characters||nchar and nvarchar: can store up to 4000 characters|
|Best suited for US English: "One problem with data types that use 1 byte to encode each character is that the data type can only represent 256 different characters. This forces multiple encoding specifications (or code pages) for different alphabets such as European alphabets, which are relatively small. It is also impossible to handle systems such as the Japanese Kanji or Korean Hangul alphabets that have thousands of characters."1||Best suited for systems that need to support at least one foreign language: "The Unicode specification defines a single encoding scheme for most characters widely used in businesses around the world. All computers consistently translate the bit patterns in Unicode data into characters using the single Unicode specification. This ensures that the same bit pattern is always converted to the same character on all computers. Data can be freely transferred from one database or computer to another without concern that the receiving system will translate the bit patterns into characters incorrectly.|