Hello,
I am trying to setup replication for a database and I get the following
error. This is the content database of WSS. I noticed that the collation was
set for: Latin1_General_CI_AS_KS_WS which is diffent from our normal
collation setting SQL_Latin1_General_CP1_CI_AS, however I created the
rplDatabase with the same collation. Any help would be greatly appreciated.
Jake
Error Message:
The schema script '\\SERVER\D$\Program Files\Microsoft SQL
Server\MSSQL$DBSERVER\ReplData\unc\SERVER$DBSERVER _STS_WCPC-L-02_Content_STS
_WCPC_L_02_Content\20040416221336\proc_FindDocs_16 .sch' could not be
propagated to the subscriber.
Error Details:
The schema script '\\SERVER\D$\Program Files\Microsoft SQL
Server\MSSQL$DBSERVER\ReplData\unc\SERVER$DBSERVER _STS_WCPC-L-02_Content_STS
_WCPC_L_02_Content\20040416221336\proc_FindDocs_16 .sch' could not be
propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
Cannot resolve collation conflict for equal to operation.
(Source: SERVER\DBSERVER (Data source); Error number: 446)
are you replicating to a SQL 7 database?
If you so you to configure your publication for this in the Specify
Subscriber Types dialog box of the create publication wizard. Otherwise in
the specify articles dialog of the same wizard click on the browse button to
the right of the articles and in the snpashot tab, select the collation tab.
"Jake" <rondican@.hotmail.com> wrote in message
news:%23RV1LCEJEHA.2380@.TK2MSFTNGP09.phx.gbl...
> Hello,
> I am trying to setup replication for a database and I get the
following
> error. This is the content database of WSS. I noticed that the collation
was
> set for: Latin1_General_CI_AS_KS_WS which is diffent from our normal
> collation setting SQL_Latin1_General_CP1_CI_AS, however I created the
> rplDatabase with the same collation. Any help would be greatly
appreciated.
> Jake
> Error Message:
> The schema script '\\SERVER\D$\Program Files\Microsoft SQL
>
Server\MSSQL$DBSERVER\ReplData\unc\SERVER$DBSERVER _STS_WCPC-L-02_Content_STS
> _WCPC_L_02_Content\20040416221336\proc_FindDocs_16 .sch' could not be
> propagated to the subscriber.
> Error Details:
> The schema script '\\SERVER\D$\Program Files\Microsoft SQL
>
Server\MSSQL$DBSERVER\ReplData\unc\SERVER$DBSERVER _STS_WCPC-L-02_Content_STS
> _WCPC_L_02_Content\20040416221336\proc_FindDocs_16 .sch' could not be
> propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ----
--
> --
> Cannot resolve collation conflict for equal to operation.
> (Source: SERVER\DBSERVER (Data source); Error number: 446)
> ----
--
> --
>
|||Jake,
Am I right to conclude that you have included the stored procedure
[proc_FindDocs.....] as an article in your publication? If yes, then the
error is occurring while applying the stored procedure to the subscriber,
because it contains code that is comparing two values (e.g. columns or
variables) of different data types. You could try to apply the stored
procedure script manually (through Query Analyser) to the subscriber
database to see if you get the same error. If yes, then analyse the stored
procedure to see which columns are involved and check their collation. This
should give you an indication of where the collation problem is occurring.
Hope the above helps.
Raj Moloye
Showing posts with label setup. Show all posts
Showing posts with label setup. Show all posts
Wednesday, March 21, 2012
Wednesday, March 7, 2012
Help - setup Sql Server 2000 on server on network
Hello -
I have a VB6 application that is hooked up to a Sql Server database on my
workstation computer. I will be distributing this application and have to
install Sql Server 2000 on a server. I have never set up Sql Server on a
network server before. Please tell me if the following steps are correct:
1. Set up Windows 2000 Server operating system on the machine (they want me
to use a separate computer from our other servers).
2. Connect to the network.
3. Install Sql Server 2000 on the machine.
4. Copy the MDF and LDF files from my workstation computer to Sql Server
2000 on the server into the ../MSSQL/Data file.
According to my logic (or lack thereof, as the case may be), my application
should be able to connect to this database from any computer in the
organization via a connection string (which is located in my application)
like the following:
"Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=MyDatabase;Data
Source=NewServerThatSqlServerWasJustInst
alledOn"
Any comments and suggestions will be greatly appreciated!
--
SandySandy,
It basically sounds like you're trying to move a SQL database from one
instance of SQL Server to another and then connect to that new instance via
your client application. That is not an issue as long as the client
application has the necessary connection information/string to the new
instance and the network connectivity is present. However, there may be
some issues with security as any logins will not be transfered because they
are stored in the Master system database and not in the end-user database
(only contains the db users). As such you may want to view the Microsoft KB
article #246133.
HTH
Jerry
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:57C7E2E5-6906-4B47-BE22-71983B3A6DF8@.microsoft.com...
> Hello -
> I have a VB6 application that is hooked up to a Sql Server database on my
> workstation computer. I will be distributing this application and have to
> install Sql Server 2000 on a server. I have never set up Sql Server on a
> network server before. Please tell me if the following steps are correct:
> 1. Set up Windows 2000 Server operating system on the machine (they want
> me
> to use a separate computer from our other servers).
> 2. Connect to the network.
> 3. Install Sql Server 2000 on the machine.
> 4. Copy the MDF and LDF files from my workstation computer to Sql Server
> 2000 on the server into the ../MSSQL/Data file.
> According to my logic (or lack thereof, as the case may be), my
> application
> should be able to connect to this database from any computer in the
> organization via a connection string (which is located in my application)
> like the following:
> "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> Info=False;Initial Catalog=MyDatabase;Data
> Source=NewServerThatSqlServerWasJustInst
alledOn"
> Any comments and suggestions will be greatly appreciated!
> --
> Sandy|||Hi Jerry -
Thanks for your response! You are correct; that's essentially what I want
to do. I just wanted to make sure I had my steps correct and that I wasn't
forgetting anything.
In looking at my "list" again, I did forget that I have to be sure to put
the log on a separate drive on the server.
Anything else I may have overlooked?
Thanks for bringing the security issue to my attention!
Sandy
"Jerry Spivey" wrote:
> Sandy,
> It basically sounds like you're trying to move a SQL database from one
> instance of SQL Server to another and then connect to that new instance vi
a
> your client application. That is not an issue as long as the client
> application has the necessary connection information/string to the new
> instance and the network connectivity is present. However, there may be
> some issues with security as any logins will not be transfered because the
y
> are stored in the Master system database and not in the end-user database
> (only contains the db users). As such you may want to view the Microsoft
KB
> article #246133.
> HTH
> Jerry
> "Sandy" <Sandy@.discussions.microsoft.com> wrote in message
> news:57C7E2E5-6906-4B47-BE22-71983B3A6DF8@.microsoft.com...
>
>
I have a VB6 application that is hooked up to a Sql Server database on my
workstation computer. I will be distributing this application and have to
install Sql Server 2000 on a server. I have never set up Sql Server on a
network server before. Please tell me if the following steps are correct:
1. Set up Windows 2000 Server operating system on the machine (they want me
to use a separate computer from our other servers).
2. Connect to the network.
3. Install Sql Server 2000 on the machine.
4. Copy the MDF and LDF files from my workstation computer to Sql Server
2000 on the server into the ../MSSQL/Data file.
According to my logic (or lack thereof, as the case may be), my application
should be able to connect to this database from any computer in the
organization via a connection string (which is located in my application)
like the following:
"Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=MyDatabase;Data
Source=NewServerThatSqlServerWasJustInst
alledOn"
Any comments and suggestions will be greatly appreciated!
--
SandySandy,
It basically sounds like you're trying to move a SQL database from one
instance of SQL Server to another and then connect to that new instance via
your client application. That is not an issue as long as the client
application has the necessary connection information/string to the new
instance and the network connectivity is present. However, there may be
some issues with security as any logins will not be transfered because they
are stored in the Master system database and not in the end-user database
(only contains the db users). As such you may want to view the Microsoft KB
article #246133.
HTH
Jerry
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:57C7E2E5-6906-4B47-BE22-71983B3A6DF8@.microsoft.com...
> Hello -
> I have a VB6 application that is hooked up to a Sql Server database on my
> workstation computer. I will be distributing this application and have to
> install Sql Server 2000 on a server. I have never set up Sql Server on a
> network server before. Please tell me if the following steps are correct:
> 1. Set up Windows 2000 Server operating system on the machine (they want
> me
> to use a separate computer from our other servers).
> 2. Connect to the network.
> 3. Install Sql Server 2000 on the machine.
> 4. Copy the MDF and LDF files from my workstation computer to Sql Server
> 2000 on the server into the ../MSSQL/Data file.
> According to my logic (or lack thereof, as the case may be), my
> application
> should be able to connect to this database from any computer in the
> organization via a connection string (which is located in my application)
> like the following:
> "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> Info=False;Initial Catalog=MyDatabase;Data
> Source=NewServerThatSqlServerWasJustInst
alledOn"
> Any comments and suggestions will be greatly appreciated!
> --
> Sandy|||Hi Jerry -
Thanks for your response! You are correct; that's essentially what I want
to do. I just wanted to make sure I had my steps correct and that I wasn't
forgetting anything.
In looking at my "list" again, I did forget that I have to be sure to put
the log on a separate drive on the server.
Anything else I may have overlooked?
Thanks for bringing the security issue to my attention!
Sandy
"Jerry Spivey" wrote:
> Sandy,
> It basically sounds like you're trying to move a SQL database from one
> instance of SQL Server to another and then connect to that new instance vi
a
> your client application. That is not an issue as long as the client
> application has the necessary connection information/string to the new
> instance and the network connectivity is present. However, there may be
> some issues with security as any logins will not be transfered because the
y
> are stored in the Master system database and not in the end-user database
> (only contains the db users). As such you may want to view the Microsoft
KB
> article #246133.
> HTH
> Jerry
> "Sandy" <Sandy@.discussions.microsoft.com> wrote in message
> news:57C7E2E5-6906-4B47-BE22-71983B3A6DF8@.microsoft.com...
>
>
Help - setup Sql Server 2000 on server on network
Hello -
I have a VB6 application that is hooked up to a Sql Server database on my
workstation computer. I will be distributing this application and have to
install Sql Server 2000 on a server. I have never set up Sql Server on a
network server before. Please tell me if the following steps are correct:
1. Set up Windows 2000 Server operating system on the machine (they want me
to use a separate computer from our other servers).
2. Connect to the network.
3. Install Sql Server 2000 on the machine.
4. Copy the MDF and LDF files from my workstation computer to Sql Server
2000 on the server into the ../MSSQL/Data file.
According to my logic (or lack thereof, as the case may be), my application
should be able to connect to this database from any computer in the
organization via a connection string (which is located in my application)
like the following:
"Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=MyDatabase;Data
Source=NewServerThatSqlServerWasJustInstalledOn"
Any comments and suggestions will be greatly appreciated!
--
SandySandy,
It basically sounds like you're trying to move a SQL database from one
instance of SQL Server to another and then connect to that new instance via
your client application. That is not an issue as long as the client
application has the necessary connection information/string to the new
instance and the network connectivity is present. However, there may be
some issues with security as any logins will not be transfered because they
are stored in the Master system database and not in the end-user database
(only contains the db users). As such you may want to view the Microsoft KB
article #246133.
HTH
Jerry
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:57C7E2E5-6906-4B47-BE22-71983B3A6DF8@.microsoft.com...
> Hello -
> I have a VB6 application that is hooked up to a Sql Server database on my
> workstation computer. I will be distributing this application and have to
> install Sql Server 2000 on a server. I have never set up Sql Server on a
> network server before. Please tell me if the following steps are correct:
> 1. Set up Windows 2000 Server operating system on the machine (they want
> me
> to use a separate computer from our other servers).
> 2. Connect to the network.
> 3. Install Sql Server 2000 on the machine.
> 4. Copy the MDF and LDF files from my workstation computer to Sql Server
> 2000 on the server into the ../MSSQL/Data file.
> According to my logic (or lack thereof, as the case may be), my
> application
> should be able to connect to this database from any computer in the
> organization via a connection string (which is located in my application)
> like the following:
> "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> Info=False;Initial Catalog=MyDatabase;Data
> Source=NewServerThatSqlServerWasJustInstalledOn"
> Any comments and suggestions will be greatly appreciated!
> --
> Sandy|||Hi Jerry -
Thanks for your response! You are correct; that's essentially what I want
to do. I just wanted to make sure I had my steps correct and that I wasn't
forgetting anything.
In looking at my "list" again, I did forget that I have to be sure to put
the log on a separate drive on the server.
Anything else I may have overlooked?
Thanks for bringing the security issue to my attention!
--
Sandy
"Jerry Spivey" wrote:
> Sandy,
> It basically sounds like you're trying to move a SQL database from one
> instance of SQL Server to another and then connect to that new instance via
> your client application. That is not an issue as long as the client
> application has the necessary connection information/string to the new
> instance and the network connectivity is present. However, there may be
> some issues with security as any logins will not be transfered because they
> are stored in the Master system database and not in the end-user database
> (only contains the db users). As such you may want to view the Microsoft KB
> article #246133.
> HTH
> Jerry
> "Sandy" <Sandy@.discussions.microsoft.com> wrote in message
> news:57C7E2E5-6906-4B47-BE22-71983B3A6DF8@.microsoft.com...
> > Hello -
> >
> > I have a VB6 application that is hooked up to a Sql Server database on my
> > workstation computer. I will be distributing this application and have to
> > install Sql Server 2000 on a server. I have never set up Sql Server on a
> > network server before. Please tell me if the following steps are correct:
> >
> > 1. Set up Windows 2000 Server operating system on the machine (they want
> > me
> > to use a separate computer from our other servers).
> >
> > 2. Connect to the network.
> >
> > 3. Install Sql Server 2000 on the machine.
> >
> > 4. Copy the MDF and LDF files from my workstation computer to Sql Server
> > 2000 on the server into the ../MSSQL/Data file.
> >
> > According to my logic (or lack thereof, as the case may be), my
> > application
> > should be able to connect to this database from any computer in the
> > organization via a connection string (which is located in my application)
> > like the following:
> >
> > "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> > Info=False;Initial Catalog=MyDatabase;Data
> > Source=NewServerThatSqlServerWasJustInstalledOn"
> >
> > Any comments and suggestions will be greatly appreciated!
> > --
> > Sandy
>
>
I have a VB6 application that is hooked up to a Sql Server database on my
workstation computer. I will be distributing this application and have to
install Sql Server 2000 on a server. I have never set up Sql Server on a
network server before. Please tell me if the following steps are correct:
1. Set up Windows 2000 Server operating system on the machine (they want me
to use a separate computer from our other servers).
2. Connect to the network.
3. Install Sql Server 2000 on the machine.
4. Copy the MDF and LDF files from my workstation computer to Sql Server
2000 on the server into the ../MSSQL/Data file.
According to my logic (or lack thereof, as the case may be), my application
should be able to connect to this database from any computer in the
organization via a connection string (which is located in my application)
like the following:
"Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=MyDatabase;Data
Source=NewServerThatSqlServerWasJustInstalledOn"
Any comments and suggestions will be greatly appreciated!
--
SandySandy,
It basically sounds like you're trying to move a SQL database from one
instance of SQL Server to another and then connect to that new instance via
your client application. That is not an issue as long as the client
application has the necessary connection information/string to the new
instance and the network connectivity is present. However, there may be
some issues with security as any logins will not be transfered because they
are stored in the Master system database and not in the end-user database
(only contains the db users). As such you may want to view the Microsoft KB
article #246133.
HTH
Jerry
"Sandy" <Sandy@.discussions.microsoft.com> wrote in message
news:57C7E2E5-6906-4B47-BE22-71983B3A6DF8@.microsoft.com...
> Hello -
> I have a VB6 application that is hooked up to a Sql Server database on my
> workstation computer. I will be distributing this application and have to
> install Sql Server 2000 on a server. I have never set up Sql Server on a
> network server before. Please tell me if the following steps are correct:
> 1. Set up Windows 2000 Server operating system on the machine (they want
> me
> to use a separate computer from our other servers).
> 2. Connect to the network.
> 3. Install Sql Server 2000 on the machine.
> 4. Copy the MDF and LDF files from my workstation computer to Sql Server
> 2000 on the server into the ../MSSQL/Data file.
> According to my logic (or lack thereof, as the case may be), my
> application
> should be able to connect to this database from any computer in the
> organization via a connection string (which is located in my application)
> like the following:
> "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> Info=False;Initial Catalog=MyDatabase;Data
> Source=NewServerThatSqlServerWasJustInstalledOn"
> Any comments and suggestions will be greatly appreciated!
> --
> Sandy|||Hi Jerry -
Thanks for your response! You are correct; that's essentially what I want
to do. I just wanted to make sure I had my steps correct and that I wasn't
forgetting anything.
In looking at my "list" again, I did forget that I have to be sure to put
the log on a separate drive on the server.
Anything else I may have overlooked?
Thanks for bringing the security issue to my attention!
--
Sandy
"Jerry Spivey" wrote:
> Sandy,
> It basically sounds like you're trying to move a SQL database from one
> instance of SQL Server to another and then connect to that new instance via
> your client application. That is not an issue as long as the client
> application has the necessary connection information/string to the new
> instance and the network connectivity is present. However, there may be
> some issues with security as any logins will not be transfered because they
> are stored in the Master system database and not in the end-user database
> (only contains the db users). As such you may want to view the Microsoft KB
> article #246133.
> HTH
> Jerry
> "Sandy" <Sandy@.discussions.microsoft.com> wrote in message
> news:57C7E2E5-6906-4B47-BE22-71983B3A6DF8@.microsoft.com...
> > Hello -
> >
> > I have a VB6 application that is hooked up to a Sql Server database on my
> > workstation computer. I will be distributing this application and have to
> > install Sql Server 2000 on a server. I have never set up Sql Server on a
> > network server before. Please tell me if the following steps are correct:
> >
> > 1. Set up Windows 2000 Server operating system on the machine (they want
> > me
> > to use a separate computer from our other servers).
> >
> > 2. Connect to the network.
> >
> > 3. Install Sql Server 2000 on the machine.
> >
> > 4. Copy the MDF and LDF files from my workstation computer to Sql Server
> > 2000 on the server into the ../MSSQL/Data file.
> >
> > According to my logic (or lack thereof, as the case may be), my
> > application
> > should be able to connect to this database from any computer in the
> > organization via a connection string (which is located in my application)
> > like the following:
> >
> > "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> > Info=False;Initial Catalog=MyDatabase;Data
> > Source=NewServerThatSqlServerWasJustInstalledOn"
> >
> > Any comments and suggestions will be greatly appreciated!
> > --
> > Sandy
>
>
Help - Rebuild System Databases on a clustered instance
I am in a DR senario and I am having trouble rebuilding the system databases on my SQL 2005 cluster.
I run the following string:
start /wait setup.exe /qn VS=Vname INSTANCENAME=instname REINSTALL=SQL_Engine REBUILDDATABASE=1 ADMINPASSWORD=password SQLACCOUNT=domain\acct SQLPASSWORD=password AGTACCOUNT=domain\acct AGTPASSWORD=password REINSTALLMODE=vomus
The setup fails with the following error:
Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows Server 2003 family, Service Pack 1 (Build 3790)
Time : Wed Dec 13 15:41:44 2006
CLUSTERSVR1 : To install Microsoft SQL Server 2005, COM+ should work.
CLUSTERSVR1 : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
CLUSTERSVR1 : To install Microsoft SQL Server 2005, COM+ should work.
CLUSTERSVR1 : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
Machine : CLUSTERSVR1
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Error Number : 5897
SQL 2005 was originally installed in May '06 as RTM. SP1 applied in September '06.
I have the original RTM install disk but obviously SP1 is causing rebuild to fail.
Can anyone advise on this please.
D.
Can you apply SP1 and then retry the procedure?
I mean doing the setup of 2005, applying SP1 and then retrying?
|||JohDas,
Unfortunately I can't.
Don't forget I do not have any databases - system or user. Therefore SP1 cannot authenticate to SQL Server to process the upgrade.
I have a bad feeling that my only option is to uninstall/reinstall SQL 2005.
But this is a last resort and I want to avaoid it if I can.
D.
Subscribe to:
Posts (Atom)