<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SQL Server Q&#38;A &#187; name</title>
	<atom:link href="http://jack-fx.com/sqlqa/tag/name/feed/" rel="self" type="application/rss+xml" />
	<link>http://jack-fx.com/sqlqa</link>
	<description>SQL Server Questions and Answers, SQL QA</description>
	<lastBuildDate>Fri, 10 Feb 2012 05:26:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Error message when you try to set a witness in a database mirroring session in SQL Server 2005: &#8220;The ALTER DATABASE command could not be sent to the remote server instance &#8216;TCP://&lt;ServerName&amp;g &#8230;</title>
		<link>http://jack-fx.com/sqlqa/2011/11/01/error-message-when-you-try-to-set-a-witness-in-a-database-mirroring-session-in-sql-server-2005-the-alter-database-command-could-not-be-sent-to-the-remote-server-instance-tcpservernameg-2/</link>
		<comments>http://jack-fx.com/sqlqa/2011/11/01/error-message-when-you-try-to-set-a-witness-in-a-database-mirroring-session-in-sql-server-2005-the-alter-database-command-could-not-be-sent-to-the-remote-server-instance-tcpservernameg-2/#comments</comments>
		<pubDate>Tue, 01 Nov 2011 10:48:13 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[ALTER DATABASE]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[database command]]></category>
		<category><![CDATA[microsoft sql server]]></category>
		<category><![CDATA[microsoft sql server 2005]]></category>
		<category><![CDATA[mirroring]]></category>
		<category><![CDATA[name]]></category>
		<category><![CDATA[principal server]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[sql server 2005]]></category>
		<category><![CDATA[Verify]]></category>
		<category><![CDATA[witness]]></category>

		<guid isPermaLink="false">http://jack-fx.com/sqlqa/2011/11/01/error-message-when-you-try-to-set-a-witness-in-a-database-mirroring-session-in-sql-server-2005-the-alter-database-command-could-not-be-sent-to-the-remote-server-instance-tcpservernameg-2/</guid>
		<description><![CDATA[SymptomsConsider the following scenario:You have a database mirroring session in Microsoft SQL Server 2005. The database mirroring session does not have a witness. You set up a witness server. On the principal server and on the witness server, you do not use DNS together with DHCP for name resolution. Instead, you specify that a host [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/sqlqa/2011/11/01/error-message-when-you-try-to-set-a-witness-in-a-database-mirroring-session-in-sql-server-2005-the-alter-database-command-could-not-be-sent-to-the-remote-server-instance-tcpservernameg-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FIX: DB-Library sp_cursor Fails with Error Message 16933 if Bracketed Identifiers are Passed with the Tablename Parameter</title>
		<link>http://jack-fx.com/sqlqa/2010/04/28/fix-db-library-sp_cursor-fails-with-error-message-16933-if-bracketed-identifiers-are-passed-with-the-tablename-parameter/</link>
		<comments>http://jack-fx.com/sqlqa/2010/04/28/fix-db-library-sp_cursor-fails-with-error-message-16933-if-bracketed-identifiers-are-passed-with-the-tablename-parameter/#comments</comments>
		<pubDate>Thu, 29 Apr 2010 04:40:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[cursor]]></category>
		<category><![CDATA[DB-Library]]></category>
		<category><![CDATA[library api]]></category>
		<category><![CDATA[maximum length]]></category>
		<category><![CDATA[name]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[server cursors]]></category>
		<category><![CDATA[server message]]></category>
		<category><![CDATA[table]]></category>

		<guid isPermaLink="false">http://jack-fx.com/sqlqa/2010/04/28/fix-db-library-sp_cursor-fails-with-error-message-16933-if-bracketed-identifiers-are-passed-with-the-tablename-parameter/</guid>
		<description><![CDATA[SymptomsWhen you use the DB-Library API server cursors, if the table name parameter that is passed to the sp_cursor stored procedure includes a bracketed identifier, the execution of sp_cursor fails with the following error message:
SQL Server message 16933, state 2, severity 16:The cursor does not include the table being modified or the table is not [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/sqlqa/2010/04/28/fix-db-library-sp_cursor-fails-with-error-message-16933-if-bracketed-identifiers-are-passed-with-the-tablename-parameter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>FIX: Configuration Fails Pasting Distributor Database Name with a Leading Space</title>
		<link>http://jack-fx.com/sqlqa/2010/04/25/fix-configuration-fails-pasting-distributor-database-name-with-a-leading-space/</link>
		<comments>http://jack-fx.com/sqlqa/2010/04/25/fix-configuration-fails-pasting-distributor-database-name-with-a-leading-space/#comments</comments>
		<pubDate>Sun, 25 Apr 2010 23:07:58 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[character]]></category>
		<category><![CDATA[configure publishing]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[database name]]></category>
		<category><![CDATA[Distribution]]></category>
		<category><![CDATA[distribution database]]></category>
		<category><![CDATA[distribution wizard]]></category>
		<category><![CDATA[name]]></category>
		<category><![CDATA[space]]></category>
		<category><![CDATA[space character]]></category>

		<guid isPermaLink="false">http://jack-fx.com/sqlqa/2010/04/25/fix-configuration-fails-pasting-distributor-database-name-with-a-leading-space/</guid>
		<description><![CDATA[SymptomsIn the Configure Publishing and Distribution Wizard, if you select the option to customize the settings rather than accept the default values, you are given the opportunity to change the distribution database name from its default of &#8220;distribution.&#8221; Although you cannot type a space character in the Distribution Database Name box, it does accept a [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/sqlqa/2010/04/25/fix-configuration-fails-pasting-distributor-database-name-with-a-leading-space/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Error message when you try to set a witness in a database mirroring session in SQL Server 2005: &#8220;The ALTER DATABASE command could not be sent to the remote server instance &#8216;TCP://&lt;ServerName&amp;g &#8230;</title>
		<link>http://jack-fx.com/sqlqa/2010/03/14/error-message-when-you-try-to-set-a-witness-in-a-database-mirroring-session-in-sql-server-2005-the-alter-database-command-could-not-be-sent-to-the-remote-server-instance-tcpservernameg/</link>
		<comments>http://jack-fx.com/sqlqa/2010/03/14/error-message-when-you-try-to-set-a-witness-in-a-database-mirroring-session-in-sql-server-2005-the-alter-database-command-could-not-be-sent-to-the-remote-server-instance-tcpservernameg/#comments</comments>
		<pubDate>Mon, 15 Mar 2010 04:40:38 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[configuration]]></category>
		<category><![CDATA[ALTER DATABASE]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[database command]]></category>
		<category><![CDATA[microsoft sql server]]></category>
		<category><![CDATA[microsoft sql server 2005]]></category>
		<category><![CDATA[mirroring]]></category>
		<category><![CDATA[name]]></category>
		<category><![CDATA[principal server]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[sql server 2005]]></category>
		<category><![CDATA[Verify]]></category>
		<category><![CDATA[witness]]></category>

		<guid isPermaLink="false">http://jack-fx.com/sqlqa/2010/03/14/error-message-when-you-try-to-set-a-witness-in-a-database-mirroring-session-in-sql-server-2005-the-alter-database-command-could-not-be-sent-to-the-remote-server-instance-tcpservernameg/</guid>
		<description><![CDATA[SymptomsConsider the following scenario:You have a database mirroring session in Microsoft SQL Server 2005. The database mirroring session does not have a witness. You set up a witness server. On the principal server and on the witness server, you do not use DNS together with DHCP for name resolution. Instead, you specify that a host [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/sqlqa/2010/03/14/error-message-when-you-try-to-set-a-witness-in-a-database-mirroring-session-in-sql-server-2005-the-alter-database-command-could-not-be-sent-to-the-remote-server-instance-tcpservernameg/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Error message when you install SQL Server 2005 Express Edition Service Pack 1 in Windows Vista: &#8220;Windows NT user or group &#8216;&lt;COMPUTERNAME&gt;\SQLServer2005MSSQLUser$&lt;COMPUTERNAME&gt;$MSSQLSE &#8230;</title>
		<link>http://jack-fx.com/sqlqa/2010/03/01/error-message-when-you-install-sql-server-2005-express-edition-service-pack-1-in-windows-vista-windows-nt-user-or-group-computernamesqlserver2005mssqlusercomputernamemssqlse/</link>
		<comments>http://jack-fx.com/sqlqa/2010/03/01/error-message-when-you-install-sql-server-2005-express-edition-service-pack-1-in-windows-vista-windows-nt-user-or-group-computernamesqlserver2005mssqlusercomputernamemssqlse/#comments</comments>
		<pubDate>Tue, 02 Mar 2010 05:13:08 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[exception]]></category>
		<category><![CDATA[computer]]></category>
		<category><![CDATA[microsoft sql server]]></category>
		<category><![CDATA[microsoft sql server 2005 express]]></category>
		<category><![CDATA[name]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[server error logs]]></category>
		<category><![CDATA[SQL]]></category>
		<category><![CDATA[sql server 2005 express]]></category>
		<category><![CDATA[sql server service]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://jack-fx.com/sqlqa/2010/03/01/error-message-when-you-install-sql-server-2005-express-edition-service-pack-1-in-windows-vista-windows-nt-user-or-group-computernamesqlserver2005mssqlusercomputernamemssqlse/</guid>
		<description><![CDATA[SymptomsWhen you try to install Microsoft SQL Server 2005 Express Edition Service Pack 1 (SP1) on a computer that is running Windows Vista, you receive the following error message:
SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Windows NT user or group &#8216;COMPUTERNAME\SQLServer2005MSSQLUser$COMPUTERNAME$MSSQLSERVER&#8217; not found. Check the [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/sqlqa/2010/03/01/error-message-when-you-install-sql-server-2005-express-edition-service-pack-1-in-windows-vista-windows-nt-user-or-group-computernamesqlserver2005mssqlusercomputernamemssqlse/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>DSN network library shown as &#8220;Other&#8221; in ODBC Administrator</title>
		<link>http://jack-fx.com/sqlqa/2010/02/24/dsn-network-library-shown-as-other-in-odbc-administrator/</link>
		<comments>http://jack-fx.com/sqlqa/2010/02/24/dsn-network-library-shown-as-other-in-odbc-administrator/#comments</comments>
		<pubDate>Thu, 25 Feb 2010 08:27:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[configuration]]></category>
		<category><![CDATA[Data]]></category>
		<category><![CDATA[data source name]]></category>
		<category><![CDATA[library]]></category>
		<category><![CDATA[lowercase letters]]></category>
		<category><![CDATA[name]]></category>
		<category><![CDATA[Network]]></category>
		<category><![CDATA[odbc api]]></category>
		<category><![CDATA[source]]></category>
		<category><![CDATA[source administrator]]></category>
		<category><![CDATA[sql server data]]></category>

		<guid isPermaLink="false">http://jack-fx.com/sqlqa/2010/02/24/dsn-network-library-shown-as-other-in-odbc-administrator/</guid>
		<description><![CDATA[Symptoms When creating a new SQL Server Data Source Name (DSN) using		the ODBC API SQLConfigDataSource function, a network library must be specified. If the network		library name is in lowercase letters, the Client Configuration dialog box may show it as &#8220;Other&#8221;. Resolution In Control Panel, the Client Configuration dialog box in ODBC Data Source Administrator is [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/sqlqa/2010/02/24/dsn-network-library-shown-as-other-in-odbc-administrator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Description of names and IP addresses that an MSDTC client in a cluster environment must have</title>
		<link>http://jack-fx.com/sqlqa/2010/02/21/description-of-names-and-ip-addresses-that-an-msdtc-client-in-a-cluster-environment-must-have/</link>
		<comments>http://jack-fx.com/sqlqa/2010/02/21/description-of-names-and-ip-addresses-that-an-msdtc-client-in-a-cluster-environment-must-have/#comments</comments>
		<pubDate>Mon, 22 Feb 2010 09:39:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[configuration]]></category>
		<category><![CDATA[client]]></category>
		<category><![CDATA[client computer name]]></category>
		<category><![CDATA[cluster]]></category>
		<category><![CDATA[computer]]></category>
		<category><![CDATA[firewall rules]]></category>
		<category><![CDATA[internet information server]]></category>
		<category><![CDATA[internet protocol ip]]></category>
		<category><![CDATA[microsoft cluster server]]></category>
		<category><![CDATA[name]]></category>
		<category><![CDATA[Server]]></category>

		<guid isPermaLink="false">http://jack-fx.com/sqlqa/2010/02/21/description-of-names-and-ip-addresses-that-an-msdtc-client-in-a-cluster-environment-must-have/</guid>
		<description><![CDATA[Symptoms The purpose of this article is to help you in the setup or		in the troubleshooting of a configuration for a COM+ Application Server or a		configuration for an Internet Information Server (IIS) computer that interacts		with a clustered server that uses Microsoft Cluster Server (MSCS) that is		behind a firewall.  You may have one of the [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/sqlqa/2010/02/21/description-of-names-and-ip-addresses-that-an-msdtc-client-in-a-cluster-environment-must-have/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>BUG: Cannot connect to a clustered named instance through a firewall</title>
		<link>http://jack-fx.com/sqlqa/2010/02/03/bug-cannot-connect-to-a-clustered-named-instance-through-a-firewall/</link>
		<comments>http://jack-fx.com/sqlqa/2010/02/03/bug-cannot-connect-to-a-clustered-named-instance-through-a-firewall/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 03:18:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[configuration]]></category>
		<category><![CDATA[client]]></category>
		<category><![CDATA[cluster node]]></category>
		<category><![CDATA[destination tcp port]]></category>
		<category><![CDATA[firewall configuration]]></category>
		<category><![CDATA[instance]]></category>
		<category><![CDATA[name]]></category>
		<category><![CDATA[network trace]]></category>
		<category><![CDATA[port 1434]]></category>
		<category><![CDATA[Server]]></category>
		<category><![CDATA[SQL]]></category>

		<guid isPermaLink="false">http://jack-fx.com/sqlqa/2010/02/03/bug-cannot-connect-to-a-clustered-named-instance-through-a-firewall/</guid>
		<description><![CDATA[SymptomsIf you try to connect a clustered named instance of SQL Server through a firewall, and you use only the instance name (for example,SQL_Virtual_Name\Instance_Name) in the connection string, the connection fails and you may receive one of the following error messages:Error message 1
Specified SQL server not found.Error message 2
SQL Server does not exist or access [...]]]></description>
		<wfw:commentRss>http://jack-fx.com/sqlqa/2010/02/03/bug-cannot-connect-to-a-clustered-named-instance-through-a-firewall/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

