MORE INFORMATION
This article contains the following additions to the readme:
- How To Omit the XML Header When Using the XSLT Content
Formatter
- New Setup File Names and Command Line Examples for SP1
- NSControl Upgrade Might Time Out On Large Databases
- Uninstalling Notification Services 2.0.2114.0 Unregisters
the Notification Services Documentation in Visual Studio .NET
- Using the Global Documentation Pack with Notification
Services 2.0 SP1
How To Omit the XML Header When Using the XSLT Content Formatter
In Notification Services 2.0 SP1, the XSLT content formatter was
modified to enable plain text output, as described in the SP1 Readme.txt file.
However, these changes, in combination with changes to the Microsoft.NET
Framework, cause the XSLT content formatter to write an XML declaration when
the output method is XML. The declaration written by the content formatter
looks like this:
xml version="1.0" encoding="UTF-16"
If the XML declaration is not needed in your notifications,
use the omit-xml-declaration attribute in the XSLT file to suppress it. The
following example shows a version of the NoOp.xslt file that suppresses the
declaration. This example also indents the XML to make it easier to
read:
<?xml version="1.0" encoding="UTF-8" ?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output omit-xml-declaration="yes" indent="yes"/>
<xsl:template match="*">
<xsl:copy-of select = "." />
</xsl:template>
</xsl:stylesheet>
New Setup File Names and Command Line Examples for SP1
In Notification Services 2.0 SP1, the Setup file names have
changed. If you run Setup from the command line, you must use the new file
names, not the file names provided in the "Running Setup from the Command Line"
topic in Notification Services 2.0 Books Online.
| 2.0 Filename | 2.0 SP1 Filename |
| MicrosoftSQLServerNotificationServices.exe | MSSQLNS20SP1.edition_code.language_code.exe |
| Microsoft SQL Server Notification
Services.msi | Microsoft SQL Server Notification Services 2.0
SP1.msi |
| Data1.cab | Data1.cab (same) |
| setup.exe | setup.exe (same) |
For the self-extracting executable, the edition codes are
as follows:
| Edition Name | Edition Code |
| Enterprise Edition | Ent |
| Standard Edition | Std |
For the self-extracting executable, the language codes are
as follows:
| Language Name | Language Code |
| Chinese (Simplified) | zh-CHS |
| Chinese (Traditional) | zh-CHT |
| English | en |
| French | fr |
| German | de |
| Italian | it |
| Japanese | ja |
| Korean | ko |
| Spanish | es |
The following examples show how the updated file names are
used when performing a command prompt installation.
Extracting files to C:\Temp without running Setup
This example shows how to extract the Setup files
(Setup.exe, Microsoft SQL Server Notification Services 2.0 SP1.msi, and
Data1.cab) to C:\Temp without running Setup. The downloaded file is the English
version of Enterprise Edition.
MSSQLNS20SP1.Ent.en.exe -f
C:\Temp -eInstalling all components using Windows Authentication
This example shows how to install all components of
Notification Services using Windows Authentication to install the database
components to the default instance of SQL Server. The downloaded file is the
English version of Enterprise
Edition.
MSSQLNS20SP1.Ent.en.exe -s -a -s
-v"/qn"Additional examples that use the 2.0 file names
are available in Notification Services 2.0 Books Online. Simply replace the 2.0
file name with the 2.0 SP1 file name when using the
examples.
NSControl Upgrade Might Time Out On Large Databases
If the instance or applications databases are very large,
NSControl Upgrade might time out during the upgrade process. For example, we
ran tests in which the database was on a server with a single 1.7 GHz
processor; when the application database had more than 2 gigabytes (GB) of
data, NSControl Upgrade timed out, leaving the database in an inconsistent
state. If this happens, you must restore backups of the instance and
application databases and then re-register the instance using NSControl
Register. To upgrade the instance, you will have to reduce the size of the
database by running vacuuming manually with the NSVacuum stored
procedure.
Before upgrading, we highly recommend that you back up the
instance and application databases. You should also ensure that the vacuuming
process has been removing obsolete data on a regular schedule, which reduces
that amount of event and notification data stored in the application database.
Note that vacuuming does not remove data from chronicle tables.
Uninstalling Notification Services 2.0.2114.0 Unregisters the Notification Services Documentation in Visual Studio .NET
If you have Microsoft Visual Studio .NET on the computer
where you install Notification Services, Setup registers the Notification
Services documentation with Visual Studio .NET; registering the documentation
makes it accessible within the Visual Studio .NET development environment.
However, if you uninstall Notification Services 2.0.2114.0 after installing
Notification Services 2.0 SP1, the Notification Services documentation will
disappear from the Visual Studio .NET Help pane.
Uninstalling
2.0.2114.0 removes the documentation files from their registered location. You
must run the SP1 Setup program again and repair Notification Services to
re-register the files with Visual Studio .NET.
To restore Notification Services Help in Visual Studio .NET:- Run the Notification Services 2.0 SP1 Setup program. The
Setup file is named MSSQLNS20SP1.edition_code.language_code.exe. If you did not download the Setup program, links to Setup are
available on the Web at http://www.microsoft.com/sql/ns/downloads/download.asp.
- On the Program Maintenance page, select Repair, and then
click Next.
- On the Ready to Repair the Program page, click Install. 4.
After Setup finishes, restart Visual Studio .NET.
Setup will re-register the Help files with Visual Studio
.NET, which returns the Notification Services documentation to the Help
pane.
Using the Global Documentation Pack with Notification Services 2.0 SP1
The Global Documentation Pack contains Notification Services
documentation in the following languages:
- Chinese (Simplified)
- Chinese (Traditional)
- French
- German
- Italian
- Japanese
- Korean
- Spanish
The Global Documentation Pack Setup program and
documentation were not updated for the SP1 release.
By default, the
Global Documentation Pack Setup program installs the documentation to folders
under the v2.0.2114.0\Docs folder. The Start menu shortcuts are placed in the
Microsoft SQL Server Notification Services 2.0.2114.0 Start Menu group. Even
though these are not the Notification Services 2.0 SP1 locations, leaving the
documentation in the default locations does not affect functionality.
When you run the Global Documentation Pack Setup program, you can
choose to install the files to a different folder. If you want to install the
files to the SP1 location, select the SP1 v2.0.3008.0 folder under
%PROGRAMFILES%\Microsoft SQL Server Notification Services. The Global
Documentation Pack will install the files to the Docs\<language> folders
under the v2.0.3008.0 folder .
- If you installed the Global Documentation Pack for
2.0.2114.0, and are now migrating to SP1, manually moving any Microsoft Help
2.0 files (HX*) files will break Help integration with Visual Studio .NET. If
you want to move the Global Doc Pack files, we recommend re-installing the
Global Doc Pack to the new location. The location for SP1 is
%PROGRAMFILES%\Microsoft SQL Server Notification Services\v2.0.3008.0\Docs. To
specify the location, click the Change button on the Custom Setup page. You
must select the file you are installing to activate the Change button.
- The Readme.txt file in the Global Documentation Pack is for
Notification Services 2.0.2114.0. We recommend that you copy the new Readme.txt
file from the page where you downloaded (or installed) Notification Services
2.0 SP1 and replace the 2.0.2114.0 file with the new file.
You can install the Notification Services Global
Documentation Pack from the following Microsoft Web site:
Notification
Services Product Documentation