Supplementary-Aware String Manipulation
[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]
This sample works only with SQL Server 2005 and SQL Server "Katmai". It will not work with any version of SQL Server earlier than SQL Server 2005.
The StringManipulate sample for Microsoft SQL Server demonstrates supplementary character aware string processing. This sample shows the implementation of five Transact-SQL string functions that provide the same string manipulation functions as built-in ones,
but with additional supplementary character-aware capability to handle both Unicode and supplementary character strings. The five functions are lens(), left
s(), rights(), sub
s() and replace_s() which equivalent to built-in’s LEN(), LEFT(), RIGHT(),
SUBSTRING() and REPLACE() string functions.
|When compiling common language runtime (CLR) integration samples, the path of the version of the Microsoft .NET Framework compiler that was included with SQL Server must be the first Framework directory in the PATH environment variable. The location of
the compiler that was included with SQL Server is either drive:\WINNT\Microsoft.NET\Framework\v2.0.xxxxx or
drive:\Windows\Microsoft.NET\Framework\v2.0.xxxxx, where drive is the installation drive and
xxxxx is the version of the .NET Framework that was included with SQL Server.
C:\Program Files\Microsoft SQL Server\100\Samples\Engine\Programmability\CLR\StringManipulate
A developer wants to accurately manipulate Unicode strings that contain supplementary characters.
Transact-SQL, Visual C# and Visual Basic.
The StringManipulate sample uses the following features of Microsoft SQL Server.
||CLR user-defined function
Before running this sample, make sure the following software is installed:
- Microsoft SQL Server or Microsoft SQL Server Express. You can obtain SQL Server Express free of charge from the SQL Server Express Documentation and Samples
- The AdventureWorks database which is included with SQL Server, and is also available at the SQL Server Developer
- The SQL Server Database Engine samples. These samples are included with SQL Server. You can download the latest version of the samples at the SQL Server Developer
- .NET Framework SDK 2.0 or Microsoft Visual Studio 2005. You can obtain .NET Framework SDK free of charge. See
Installing the .NET Framework SDK.
- Ext-B font must be installed on the computer for the correct characters to appear in the SQL Server Management Studio results window. To change the font in the results window, in Management Studio, on the
Tools menu, click Options, expand Environment, and then click
Fonts and Colors. Set the font to MingLiU_ExtB for Text Results and/or Grid Results. You must close and then reopen Management Studio for the changes to take effect.
Building the Sample
If you have not already created the strong-name key file ExternalSampleKey.snk
, generate the key file using the following instructions.
To generate a strong name key file
- Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to
All Programs, point to Microsoft Visual Studio 2005, point to Visual Studio Tools, and then click
Visual Studio 2005 Command Prompt.—Or—Open a Microsoft .NET Framework command prompt. Click
Start, point to All Programs, point to Microsoft .NET Framework SDK 2.0, and then click
SDK Command Prompt.
- At the command prompt, use the change directory (CD) command to change the current folder of the command prompt window to the Samples folder.
Note: To determine the folder where samples are located, click Start, point to
All Programs, point to Microsoft SQL Server, point to Documentation and Tutorials, and then click
Samples Directory. If the default installation location was used, the samples are located in <systemdrive_>:\Program Files\Microsoft SQL Server\100\Samples.
- At the command prompt, run the following command to generate the key file:
sn -k ExternalSampleKey.snk ** Important: For more information about the strong-name key pair, see "Security Briefs: Strong Names and Security in the .NET Framework" in the .NET Development Center on MSDN.To build the sample, do the
Build the sample
- Compile the sample by using Visual Studio 2005 and the provided Visual Studio solution, or by using Microsoft MSBuild, which is included in the .NET Framework SDK 2.0. Run a command similar to the following at the command prompt:
msbuild /nologo /verbosity:quiet /property:Configuration=Debug CS\ StringManipulate.sln
- Make sure that the AdventureWorks database is installed, or, if necessary, create the database in which you want to install the samples.
- If you did not install the SQL Server Database Engine samples in the default location, modify the path in the CREATE ASSEMBLY part of the script in Scripts\InstallCS.sql and Scripts\InstallVB.sql to refer to location where the samples were installed.
- Open the scripts\installCS.sql or scripts\installVB.sql file, depending on whether you compiled the Visual C# project or the Visual Basic project, in Management Studio. Run the script that is contained in the file, or run a command similar to the following
at the command prompt: sqlcmd -E -I -i Scripts\InstallCS.sql This file contains script to install and register the sample CLR objects into SQL Server.
Running the Sample
To run the sample, do the following:
Run the sample
- Open the scripts\test.sql file in SQL Server Management Studio. Run the script that is contained in the file, or run the following at the command prompt:
sqlcmd -E -I -i Scripts\test.sql This script invokes the string manipulation sample from Transact-SQL.
Removing the Sample
To remove the StringManipulate sample, do the following:
Remove the sample
- Open the scripts\cleanup.sql file in SQL Server Management Studio. Run the script that is contained in the file, or run the following at the command prompt:
sqlcmd -E -I -i Scripts\cleanup.sql This script removes the sample.
The CLR for SQL Server "Katmai" or SQL Server Express must be enabled for this sample to work correctly.
Samples are provided for educational purposes only. They are not intended to be used in a production environment and have not been tested in a production environment. Microsoft does not provide technical support for these samples. Sample applications and assemblies
should not be connected to or used with your production SQL Server database or your report server without the permission of the system administrator.
© 2007 Microsoft Corporation. All rights reserved.