I am running two instances of SQL Server 2005 Developer Edition (SP1) on the
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476
--
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
Any help would be greatly appreciated,
leilaHello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
> 6
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
> Any help would be greatly appreciated,
> leil|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews.microsoft.com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>> I am running two instances of SQL Server 2005 Developer Edition (SP1)
>> on the same machine. Both SQL Server and Agent services use a local
>> user account which is member of Windows Administrators. The wizard for
>> Enlisting TSX fails with the following report:
>> Enlist TSX Progress
>> - Create MSXOperator (Success)
>> Checking for an existing MSXOperator.
>> Updating existing MSXOperator.
>> Successfully updated MSXOperator.
>> - Make sure the Agent service for 'NIMA\sql2005_1' is running
>> (Success)
>> The service 'SQLAgent$SQL2005_1' is running.
>> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
>> Enlisting target server 'NIMA\sql2005_2' with master server
>> 'NIMA\sql2005_1'.
>> Using new enlistment method.
>> Messages
>> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
>> (Microsoft.SqlServer.Smo)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9
>> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplat
>> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
>> 6
>> --
>> ADDITIONAL INFORMATION:
>> An exception occurred while executing a Transact-SQL statement or
>> batch. (Microsoft.SqlServer.ConnectionInfo)
>> --
>> The enlist operation failed (reason: SQLServerAgent Error: Unable to
>> connect to server. .) (Microsoft SQL Server, Error: 22026)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
>> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
>> Any help would be greatly appreciated,
>> leila
>
Showing posts with label jobs. Show all posts
Showing posts with label jobs. Show all posts
Friday, March 30, 2012
Multi Server Jobs
I am running two instances of SQL Server 2005 Developer Edition (SP1) on the
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?Prod...26&LinkId=20476
Any help would be greatly appreciated,
leilaHello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...erver&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
> 6
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...erver&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
> Any help would be greatly appreciated,
> leila|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews
.microsoft.com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>sql
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
http://go.microsoft.com/fwlink?Prod...26&LinkId=20476
Any help would be greatly appreciated,
leilaHello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...erver&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=2047
> 6
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...erver&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
> Any help would be greatly appreciated,
> leila|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews
.microsoft.com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>sql
Wednesday, March 28, 2012
Multi Server Jobs
I am running two instances of SQL Server 2005 Developer Edition (SP1) on the
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=MSX+enlist+JobServer&LinkId=20476[/url]
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476[ /url]
Any help would be greatly appreciated,
leila
Hello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management. Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+J obServer&LinkId=2047
> 6
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20 476
> Any help would be greatly appreciated,
> leila
|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews.microsoft .com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>
same machine. Both SQL Server and Agent services use a local user account
which is member of Windows Administrators. The wizard for Enlisting TSX
fails with the following report:
Enlist TSX Progress
- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.
- Make sure the Agent service for 'NIMA\sql2005_1' is running (Success)
The service 'SQLAgent$SQL2005_1' is running.
- Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
Enlisting target server 'NIMA\sql2005_2' with master server
'NIMA\sql2005_1'.
Using new enlistment method.
Messages
MSX enlist failed for JobServer 'NIMA\sql2005_2'. (Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=MSX+enlist+JobServer&LinkId=20476[/url]
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to server. .) (Microsoft SQL Server, Error: 22026)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476[ /url]
Any help would be greatly appreciated,
leila
Hello Leila,
Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
SP2.
Have you tried a domain account for SQL Agent?
Simon Sabin
SQL Server MVP
http://sqlblogcasts.com/blogs/simons
> I am running two instances of SQL Server 2005 Developer Edition (SP1)
> on the same machine. Both SQL Server and Agent services use a local
> user account which is member of Windows Administrators. The wizard for
> Enlisting TSX fails with the following report:
> Enlist TSX Progress
> - Create MSXOperator (Success)
> Checking for an existing MSXOperator.
> Updating existing MSXOperator.
> Successfully updated MSXOperator.
> - Make sure the Agent service for 'NIMA\sql2005_1' is running
> (Success)
> The service 'SQLAgent$SQL2005_1' is running.
> - Enlist 'NIMA\sql2005_2' into 'NIMA\sql2005_1' (Error)
> Enlisting target server 'NIMA\sql2005_2' with master server
> 'NIMA\sql2005_1'.
> Using new enlistment method.
> Messages
> MSX enlist failed for JobServer 'NIMA\sql2005_2'.
> (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9
> .00.2047.00&EvtSrc=Microsoft.SqlServer.Management. Smo.ExceptionTemplat
> es.FailedOperationExceptionText&EvtID=MSX+enlist+J obServer&LinkId=2047
> 6
> --
> ADDITIONAL INFORMATION:
> An exception occurred while executing a Transact-SQL statement or
> batch. (Microsoft.SqlServer.ConnectionInfo)
> --
> The enlist operation failed (reason: SQLServerAgent Error: Unable to
> connect to server. .) (Microsoft SQL Server, Error: 22026)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=0
> 9.00.2047&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20 476
> Any help would be greatly appreciated,
> leila
|||Actually I don't have a domain on my notebook, I have used .\username for
agents.
"Simon Sabin" <SimonSabin@.noemail.noemail> wrote in message
news:62959f1a43cc68c90a27d3a103d4@.msnews.microsoft .com...
> Hello Leila,
> Personally MSX is really bad in RTM and SP1. a huge number of fixes are in
> SP2.
> Have you tried a domain account for SQL Agent?
> Simon Sabin
> SQL Server MVP
> http://sqlblogcasts.com/blogs/simons
>
>
Monday, March 26, 2012
Multi column primary keys
I have used full-text indexing on some of my past jobs and just recently convinced my supervisor to try it out. I had forgotten that one can only index single column primary key tables. At my current work environment we have several identical databases on
several servers. Those databases are being consolidated into another database via dts. For this reason multi-column PK's had to be set up to avoid duplication.
To rewrite the application and redesign the database is not an option. Is there a workaround to be able to index tables with multiple column PK's or do I have to give up on trying to use the FTI feature?
Ralph Schwehr
Programmer / Analyst
can you add another int column to the tables you want to FTI which has a
unique index on it?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Ralph Schwehr" <RalphSchwehr@.discussions.microsoft.com> wrote in message
news:76928EFC-6552-4AAC-9869-95DD1BAC21BF@.microsoft.com...
> I have used full-text indexing on some of my past jobs and just recently
convinced my supervisor to try it out. I had forgotten that one can only
index single column primary key tables. At my current work environment we
have several identical databases on several servers. Those databases are
being consolidated into another database via dts. For this reason
multi-column PK's had to be set up to avoid duplication.
> To rewrite the application and redesign the database is not an option. Is
there a workaround to be able to index tables with multiple column PK's or
do I have to give up on trying to use the FTI feature?
> --
> Ralph Schwehr
> Programmer / Analyst
|||Thanks Hilary,
that is what I did, although this could be propblematic when consolidating the databases into one. But I think we will just not use this new key in the consolidated database.
Ralph Schwehr
Programmer / Analyst
"Hilary Cotter" wrote:
> can you add another int column to the tables you want to FTI which has a
> unique index on it?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Ralph Schwehr" <RalphSchwehr@.discussions.microsoft.com> wrote in message
> news:76928EFC-6552-4AAC-9869-95DD1BAC21BF@.microsoft.com...
> convinced my supervisor to try it out. I had forgotten that one can only
> index single column primary key tables. At my current work environment we
> have several identical databases on several servers. Those databases are
> being consolidated into another database via dts. For this reason
> multi-column PK's had to be set up to avoid duplication.
> there a workaround to be able to index tables with multiple column PK's or
> do I have to give up on trying to use the FTI feature?
>
>
several servers. Those databases are being consolidated into another database via dts. For this reason multi-column PK's had to be set up to avoid duplication.
To rewrite the application and redesign the database is not an option. Is there a workaround to be able to index tables with multiple column PK's or do I have to give up on trying to use the FTI feature?
Ralph Schwehr
Programmer / Analyst
can you add another int column to the tables you want to FTI which has a
unique index on it?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Ralph Schwehr" <RalphSchwehr@.discussions.microsoft.com> wrote in message
news:76928EFC-6552-4AAC-9869-95DD1BAC21BF@.microsoft.com...
> I have used full-text indexing on some of my past jobs and just recently
convinced my supervisor to try it out. I had forgotten that one can only
index single column primary key tables. At my current work environment we
have several identical databases on several servers. Those databases are
being consolidated into another database via dts. For this reason
multi-column PK's had to be set up to avoid duplication.
> To rewrite the application and redesign the database is not an option. Is
there a workaround to be able to index tables with multiple column PK's or
do I have to give up on trying to use the FTI feature?
> --
> Ralph Schwehr
> Programmer / Analyst
|||Thanks Hilary,
that is what I did, although this could be propblematic when consolidating the databases into one. But I think we will just not use this new key in the consolidated database.
Ralph Schwehr
Programmer / Analyst
"Hilary Cotter" wrote:
> can you add another int column to the tables you want to FTI which has a
> unique index on it?
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Ralph Schwehr" <RalphSchwehr@.discussions.microsoft.com> wrote in message
> news:76928EFC-6552-4AAC-9869-95DD1BAC21BF@.microsoft.com...
> convinced my supervisor to try it out. I had forgotten that one can only
> index single column primary key tables. At my current work environment we
> have several identical databases on several servers. Those databases are
> being consolidated into another database via dts. For this reason
> multi-column PK's had to be set up to avoid duplication.
> there a workaround to be able to index tables with multiple column PK's or
> do I have to give up on trying to use the FTI feature?
>
>
Subscribe to:
Posts (Atom)