Error when making a transactional replication

Hi,
I'm making a transactional replication.
I get the following error:
Could not bulk insert. Bulk data stream was incorrectly specified as sorted.
(Source: SQL4 (Data source); Error number: 4819)
Function sequence error
(Source: ODBC Driver Manager (ODBC); Error number: S1010)
Anyone that knows how to solve the problem?
Thanks in advance
Anders
your collation on your publication database is different from your collation
on the subscriber database.
To solve your problem use the same collation on both databases.
"Anders Johansson" <anders.johansson@.nospam.se> wrote in message
news:OQ9CtRuJEHA.1096@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I'm making a transactional replication.
> I get the following error:
> Could not bulk insert. Bulk data stream was incorrectly specified as
sorted.
> (Source: SQL4 (Data source); Error number: 4819)
> ----
--
> --
> Function sequence error
> (Source: ODBC Driver Manager (ODBC); Error number: S1010)
> ----
--
> --
> Anyone that knows how to solve the problem?
> Thanks in advance
> Anders
>
|||Hi Hilary!
The publication database had a different collation than the subscriber.
But I didnt change the whole subscriber collation - just the article that
went wrong. (There was an alternative in the Publication properties).
Thanks!
"Hilary Cotter" <hilaryk@.att.net> skrev i meddelandet
news:%23tQRaguJEHA.3944@.tk2msftngp13.phx.gbl...
> your collation on your publication database is different from your
collation
> on the subscriber database.
> To solve your problem use the same collation on both databases.
> "Anders Johansson" <anders.johansson@.nospam.se> wrote in message
> news:OQ9CtRuJEHA.1096@.TK2MSFTNGP10.phx.gbl...
> sorted.
> ----
> --
> ----
> --
>
|||damn, why didn't I think of that. Good idea!
"Anders Johansson" <anders.johansson@.nospam.se> wrote in message
news:uYQGUquJEHA.3380@.TK2MSFTNGP09.phx.gbl...
> Hi Hilary!
> The publication database had a different collation than the subscriber.
> But I didnt change the whole subscriber collation - just the article that
> went wrong. (There was an alternative in the Publication properties).
> Thanks!
> "Hilary Cotter" <hilaryk@.att.net> skrev i meddelandet
> news:%23tQRaguJEHA.3944@.tk2msftngp13.phx.gbl...
> collation
> ----
> ----
>

Error when executing ALTER DATABASE statement

Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
ALTER DATABASE <Your database name>
SET RECOVERY FULL
but I am getting the following error:
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
Rajesh
It looks like a permission issue. Are you a member of sysadmin, dbcreator
or db_owner?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Rajesh" <Rajesh@.discussions.microsoft.com> wrote in message
news:4EC91AF7-A227-4A52-86F1-C4F0529A8AAD@.microsoft.com...
Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
ALTER DATABASE <Your database name>
SET RECOVERY FULL
but I am getting the following error:
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
Rajesh

Error when executing ALTER DATABASE statement

Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
---
ALTER DATABASE <Your database name>
SET RECOVERY FULL
----
but I am getting the following error:
----
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
----
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
RajeshIt looks like a permission issue. Are you a member of sysadmin, dbcreator
or db_owner?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Rajesh" <Rajesh@.discussions.microsoft.com> wrote in message
news:4EC91AF7-A227-4A52-86F1-C4F0529A8AAD@.microsoft.com...
Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
---
ALTER DATABASE <Your database name>
SET RECOVERY FULL
----
but I am getting the following error:
----
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
----
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
Rajesh

Error when executing ALTER DATABASE statement

Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
---
ALTER DATABASE <Your database name>
SET RECOVERY FULL
----
but I am getting the following error:
----
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
----
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
RajeshIt looks like a permission issue. Are you a member of sysadmin, dbcreator
or db_owner?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Rajesh" <Rajesh@.discussions.microsoft.com> wrote in message
news:4EC91AF7-A227-4A52-86F1-C4F0529A8AAD@.microsoft.com...
Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
---
ALTER DATABASE <Your database name>
SET RECOVERY FULL
----
but I am getting the following error:
----
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
----
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
Rajeshsql

Error using 'Do not lock tables during snapshot generation' optio

I setup a transactional recplication and selected the 'Do not lock tables
during snapshot generation' option so to allow the publication DB to be
available while snapshot is being generated. Snapshot completed OK but the
distributor returned error:
Operand type clash: uniqueidentifier is incompatible with int
(Source: SQLSERVER1\SERVER1 (Data source); Error number: 206)
However, If I unselect the 'Do not lock tables during snapshot generation',
the distributor replicated the DB without error. However, I will lock up all
tables in the Publisher while snapshot is being generated.
Thanks for your help in advance.
Do you have any computed columns in the table that is causing you problem?
If so, does the primary key contain any computed columns?
-Raymond
"Fas" <Fas@.discussions.microsoft.com> wrote in message
news:F0B380C9-53B7-44BD-A810-864B9A685E63@.microsoft.com...
>I setup a transactional recplication and selected the 'Do not lock tables
> during snapshot generation' option so to allow the publication DB to be
> available while snapshot is being generated. Snapshot completed OK but
> the
> distributor returned error:
> Operand type clash: uniqueidentifier is incompatible with int
> (Source: SQLSERVER1\SERVER1 (Data source); Error number: 206)
> However, If I unselect the 'Do not lock tables during snapshot
> generation',
> the distributor replicated the DB without error. However, I will lock up
> all
> tables in the Publisher while snapshot is being generated.
> Thanks for your help in advance.
>
>
|||Thanks for your quick response. We do not use compute columns. Looks like
load loading process mismatch the uniqueidentifier field with an int field.
Because if I do not use the 'Do not lock tables during snapshot generation'
option. the loading process completed fine. The GUID (msrepl_tran_version)
file was added to the replication articles when the articles were created and
they are all at the last column.
"Fas" wrote:

> I setup a transactional recplication and selected the 'Do not lock tables
> during snapshot generation' option so to allow the publication DB to be
> available while snapshot is being generated. Snapshot completed OK but the
> distributor returned error:
> Operand type clash: uniqueidentifier is incompatible with int
> (Source: SQLSERVER1\SERVER1 (Data source); Error number: 206)
> However, If I unselect the 'Do not lock tables during snapshot generation',
> the distributor replicated the DB without error. However, I will lock up all
> tables in the Publisher while snapshot is being generated.
> Thanks for your help in advance.
>
>
|||This sounds kind of strange or I am simply confused as enabling the "Do not
lock tables..." option doesn't change the schema that replication expects at
the subscriber. It would be great if you can post the detail error text that
you were getting (sans sensitive information) if you have determined that
this is not a simple schema mismatch issue.
-Raymond
"Fas" <Fas@.discussions.microsoft.com> wrote in message
news:318470F3-DFE0-4B18-BD9C-17107A3AB3A3@.microsoft.com...[vbcol=seagreen]
> Thanks for your quick response. We do not use compute columns. Looks
> like
> load loading process mismatch the uniqueidentifier field with an int
> field.
> Because if I do not use the 'Do not lock tables during snapshot
> generation'
> option. the loading process completed fine. The GUID
> (msrepl_tran_version)
> file was added to the replication articles when the articles were created
> and
> they are all at the last column.
>
> "Fas" wrote:

Error trying to do transactional replication on a long text column

I am getting the following error message when I try to do a transactional
replication of a large table with a text column:
Error Message: The process could not bulk copy into table '"monitorResults"'.
Error Details: Expected the text length in data stream for bulk copy of
text, ntext, or image data.
(Source: IWPSQL3 (Data source); Error number: 4813)
I checked sp_configure 'max text repl size (B)' and it is much larger than
the results from: SELECT max(datalength(notes)) FROM dbo.monitorResults
Does anyone have any ideas?
Thanks!
Racer-D
does this post help?
http://groups.google.com/groups?selm...utput =gplain
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Racer-D" <RacerD@.discussions.microsoft.com> wrote in message
news:960960F3-46E7-44C6-A46F-078D6A448DD7@.microsoft.com...
> I am getting the following error message when I try to do a transactional
> replication of a large table with a text column:
> Error Message: The process could not bulk copy into table
'"monitorResults"'.
> Error Details: Expected the text length in data stream for bulk copy of
> text, ntext, or image data.
> (Source: IWPSQL3 (Data source); Error number: 4813)
> ----
--
> I checked sp_configure 'max text repl size (B)' and it is much larger than
> the results from: SELECT max(datalength(notes)) FROM dbo.monitorResults
> Does anyone have any ideas?
> Thanks!
> Racer-D

Error to manually add subscription to an article

When trying to add an article back to an existing publication thats active
in transactional replication I get the following error
Server: Msg 14100, Level 16, State 1, Procedure sp_addsubscription, Line 240
Specify all articles when subscribing to a publication using concurrent
snapshot processing.
Apparently concurrent snapshot is enabled and when I did issue the
sp_addsubscription and specified the @.article parameter with the table name
, it didnt like it and threw the above error..
It wanted 'all' .. and I was afraid it would do some reinitializing,etc..
Just curious to know why we need that 'all'.. Seems kinda buggy
Interesting. I remember seeing this on Vyas's blog:
http://vyaskn.tripod.com/sqlblog/. He didn't report a solution and I'll also
take a look.
Rgds,
Paul Ibison
|||I just substituted all and it worked. It did take care of just the
respective articles.. Thank God..
With that Im thinking, should we just use all even if we dont have
concurrent snapshot enabled . Will it just take care of just those articles
we want to add manually. I'll try it out and let u know
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23zcnRGXSFHA.1528@.TK2MSFTNGP09.phx.gbl...
> Interesting. I remember seeing this on Vyas's blog:
> http://vyaskn.tripod.com/sqlblog/. He didn't report a solution and I'll
also
> take a look.
> Rgds,
> Paul Ibison
>
>