Ok this is really irksome

Ok so I rebuilt the replication. Using all of the default options
except snapshot location. It worked fine. The 1st time I added a
table, it worked fine.
The 2nd time I added a table it repeated what happened above --
couldn't find the SPs. I tried adding them manually but it only
created the 1st part of the INSERT sp and not the 2nd (:2).
How did you create the insert procs? If you used
sp_scriptpublicationcustomprocs make sure your results pane width is 8192 to
get the entire proc.
Another option is to use SQL statements instead of procs to apply the
transactions. Right click on your publication, select properties, click the
articles tab, click the commands tab, type SQL for insert, update, and
delete, and then regenerate and redistribute your snapshot.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Jason Wilson" <wilsonj@.ausrad.com> wrote in message
news:1159290324.749311.322320@.e3g2000cwe.googlegro ups.com...
> Ok so I rebuilt the replication. Using all of the default options
> except snapshot location. It worked fine. The 1st time I added a
> table, it worked fine.
> The 2nd time I added a table it repeated what happened above --
> couldn't find the SPs. I tried adding them manually but it only
> created the 1st part of the INSERT sp and not the 2nd (:2).
>

Off-Site SQL Server Replication

Hello
We're looking at another point of presense for our websites.
What would be the best way to keep the external sql server updated with
current data from the main server? Would a cluster license be required?
Thanks for any advice
Richard
It its one way data flow, use transactional replication. Otherwise I would
suggest merge replication or bi-directional transactional replication.
You would not require a cluster license for this - whatever that is.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Richard" <rcowell%nospam%@.britainusa.com> wrote in message
news:OjmxyB9fEHA.1984@.TK2MSFTNGP10.phx.gbl...
> Hello
> We're looking at another point of presense for our websites.
> What would be the best way to keep the external sql server updated with
> current data from the main server? Would a cluster license be required?
> Thanks for any advice
> Richard
>
|||Richard,
I'd like to know a bit more about your requirements, but firstly, is the
'other point of presence' read only or read/write? If it is read only, you
have a choice between log-shipping and transactional replication (have a
look at the articles section on http://www.replicationanswers.com/ for a
comparison of functionality).
If read/write, have a look at merge replication.
Clustering isn't suitable as it won't duplicate your data - it provides
automatic failover of the SQL server based on a single source of data - RAID
or SCSI array.
HTH,
Paul Ibison
|||Hi
The new presence will be read/write.
We currently have 2 sql servers here, one live and another backup - ideally
i'd have both of them live if possible. I'm not familiar with merge
replication, is it available in standard sql 2000?
Rich
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:ewZVoJ9fEHA.3048@.TK2MSFTNGP09.phx.gbl...
> Richard,
> I'd like to know a bit more about your requirements, but firstly, is the
> 'other point of presence' read only or read/write? If it is read only, you
> have a choice between log-shipping and transactional replication (have a
> look at the articles section on http://www.replicationanswers.com/ for a
> comparison of functionality).
> If read/write, have a look at merge replication.
> Clustering isn't suitable as it won't duplicate your data - it provides
> automatic failover of the SQL server based on a single source of data -
> RAID
> or SCSI array.
> HTH,
> Paul Ibison
>
|||Richard,
Standard Edition is fine. BOL has plenty of details on setting up merge and
here is a walkthrough you can use:
http://www.mssqlcity.com/Articles/Re...MR/SetupMR.htm
HTH,
Paul Ibison
|||That's great thanks a lot for your help, Paul & Hilary
Rich
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23jeIJV9fEHA.3964@.TK2MSFTNGP12.phx.gbl...
> Richard,
> Standard Edition is fine. BOL has plenty of details on setting up merge
> and
> here is a walkthrough you can use:
> http://www.mssqlcity.com/Articles/Re...MR/SetupMR.htm
> HTH,
> Paul Ibison
>

Offline Reporting DB...

A customer of ours was considering replication as a means of maintaining
data in a second DB on a second server for reporting use only. We think
replication is overkill since they won't mind if the data is a day or two
old.
I like the idea of simply restoring their most recent full backup on the
reporting server, but I'm not sure if they do a full backup every night.
What are other approaches that folks use to accomplish this sort of thing?
Log shipping doesn't seem right; replication seems like overkill. DTS
possibly? Any thoughts, links, or words will be greatly appreciated!
Thanks in advance for your time,
James Hunter RossWithout details about the database size, your connection bandwidth, etc.,
it's hard to say what is the best way for your needs.
If the customer can tolerate data two days old, you can use snapshot
replication and set the snapshot interval as 48 hours. Yuo can also make use
of log shipping secondary server with restored databases being in read-only
mode. Then users can run reports off the databases from time to time. The
inconvenience with log shipping is to regularly kick users out of the
database so that restore of transaction logs can go on. The third option
will be increase full backup frequency so that there is a full backup every
two days, otherwise you will have to restore from a full backup more than 2
days ago and apply all subsequent transaction logs.
Other things you can consider: will copy database wizard apply? It requires
the database being shut down.
Richard
"James Hunter Ross" <james.ross@.oneilsoft.com> wrote in message
news:OYhK%23KdcFHA.3828@.tk2msftngp13.phx.gbl...
>A customer of ours was considering replication as a means of maintaining
>data in a second DB on a second server for reporting use only. We think
>replication is overkill since they won't mind if the data is a day or two
>old.
> I like the idea of simply restoring their most recent full backup on the
> reporting server, but I'm not sure if they do a full backup every night.
> What are other approaches that folks use to accomplish this sort of thing?
> Log shipping doesn't seem right; replication seems like overkill. DTS
> possibly? Any thoughts, links, or words will be greatly appreciated!
> Thanks in advance for your time,
> James Hunter Ross
>|||Keep it simple, if possible. Backup restore is as simple as it gets, and you get your backups tested
each time.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"James Hunter Ross" <james.ross@.oneilsoft.com> wrote in message
news:OYhK%23KdcFHA.3828@.tk2msftngp13.phx.gbl...
>A customer of ours was considering replication as a means of maintaining data in a second DB on a
>second server for reporting use only. We think replication is overkill since they won't mind if
>the data is a day or two old.
> I like the idea of simply restoring their most recent full backup on the reporting server, but I'm
> not sure if they do a full backup every night.
> What are other approaches that folks use to accomplish this sort of thing? Log shipping doesn't
> seem right; replication seems like overkill. DTS possibly? Any thoughts, links, or words will be
> greatly appreciated!
> Thanks in advance for your time,
> James Hunter Ross
>|||We use log shipping for this as our main DB is too large to restore nightly.
Works well.
Mike Kruchten
"James Hunter Ross" <james.ross@.oneilsoft.com> wrote in message
news:OYhK%23KdcFHA.3828@.tk2msftngp13.phx.gbl...
>A customer of ours was considering replication as a means of maintaining
>data in a second DB on a second server for reporting use only. We think
>replication is overkill since they won't mind if the data is a day or two
>old.
> I like the idea of simply restoring their most recent full backup on the
> reporting server, but I'm not sure if they do a full backup every night.
> What are other approaches that folks use to accomplish this sort of thing?
> Log shipping doesn't seem right; replication seems like overkill. DTS
> possibly? Any thoughts, links, or words will be greatly appreciated!
> Thanks in advance for your time,
> James Hunter Ross
>

Offline Reporting DB...

A customer of ours was considering replication as a means of maintaining
data in a second DB on a second server for reporting use only. We think
replication is overkill since they won't mind if the data is a day or two
old.
I like the idea of simply restoring their most recent full backup on the
reporting server, but I'm not sure if they do a full backup every night.
What are other approaches that folks use to accomplish this sort of thing?
Log shipping doesn't seem right; replication seems like overkill. DTS
possibly? Any thoughts, links, or words will be greatly appreciated!
Thanks in advance for your time,
James Hunter Ross
Without details about the database size, your connection bandwidth, etc.,
it's hard to say what is the best way for your needs.
If the customer can tolerate data two days old, you can use snapshot
replication and set the snapshot interval as 48 hours. Yuo can also make use
of log shipping secondary server with restored databases being in read-only
mode. Then users can run reports off the databases from time to time. The
inconvenience with log shipping is to regularly kick users out of the
database so that restore of transaction logs can go on. The third option
will be increase full backup frequency so that there is a full backup every
two days, otherwise you will have to restore from a full backup more than 2
days ago and apply all subsequent transaction logs.
Other things you can consider: will copy database wizard apply? It requires
the database being shut down.
Richard
"James Hunter Ross" <james.ross@.oneilsoft.com> wrote in message
news:OYhK%23KdcFHA.3828@.tk2msftngp13.phx.gbl...
>A customer of ours was considering replication as a means of maintaining
>data in a second DB on a second server for reporting use only. We think
>replication is overkill since they won't mind if the data is a day or two
>old.
> I like the idea of simply restoring their most recent full backup on the
> reporting server, but I'm not sure if they do a full backup every night.
> What are other approaches that folks use to accomplish this sort of thing?
> Log shipping doesn't seem right; replication seems like overkill. DTS
> possibly? Any thoughts, links, or words will be greatly appreciated!
> Thanks in advance for your time,
> James Hunter Ross
>
|||Keep it simple, if possible. Backup restore is as simple as it gets, and you get your backups tested
each time.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"James Hunter Ross" <james.ross@.oneilsoft.com> wrote in message
news:OYhK%23KdcFHA.3828@.tk2msftngp13.phx.gbl...
>A customer of ours was considering replication as a means of maintaining data in a second DB on a
>second server for reporting use only. We think replication is overkill since they won't mind if
>the data is a day or two old.
> I like the idea of simply restoring their most recent full backup on the reporting server, but I'm
> not sure if they do a full backup every night.
> What are other approaches that folks use to accomplish this sort of thing? Log shipping doesn't
> seem right; replication seems like overkill. DTS possibly? Any thoughts, links, or words will be
> greatly appreciated!
> Thanks in advance for your time,
> James Hunter Ross
>
|||We use log shipping for this as our main DB is too large to restore nightly.
Works well.
Mike Kruchten
"James Hunter Ross" <james.ross@.oneilsoft.com> wrote in message
news:OYhK%23KdcFHA.3828@.tk2msftngp13.phx.gbl...
>A customer of ours was considering replication as a means of maintaining
>data in a second DB on a second server for reporting use only. We think
>replication is overkill since they won't mind if the data is a day or two
>old.
> I like the idea of simply restoring their most recent full backup on the
> reporting server, but I'm not sure if they do a full backup every night.
> What are other approaches that folks use to accomplish this sort of thing?
> Log shipping doesn't seem right; replication seems like overkill. DTS
> possibly? Any thoughts, links, or words will be greatly appreciated!
> Thanks in advance for your time,
> James Hunter Ross
>

Offline Reporting DB...

A customer of ours was considering replication as a means of maintaining
data in a second DB on a second server for reporting use only. We think
replication is overkill since they won't mind if the data is a day or two
old.
I like the idea of simply restoring their most recent full backup on the
reporting server, but I'm not sure if they do a full backup every night.
What are other approaches that folks use to accomplish this sort of thing?
Log shipping doesn't seem right; replication seems like overkill. DTS
possibly? Any thoughts, links, or words will be greatly appreciated!
Thanks in advance for your time,
James Hunter RossWithout details about the database size, your connection bandwidth, etc.,
it's hard to say what is the best way for your needs.
If the customer can tolerate data two days old, you can use snapshot
replication and set the snapshot interval as 48 hours. Yuo can also make use
of log shipping secondary server with restored databases being in read-only
mode. Then users can run reports off the databases from time to time. The
inconvenience with log shipping is to regularly kick users out of the
database so that restore of transaction logs can go on. The third option
will be increase full backup frequency so that there is a full backup every
two days, otherwise you will have to restore from a full backup more than 2
days ago and apply all subsequent transaction logs.
Other things you can consider: will copy database wizard apply? It requires
the database being shut down.
Richard
"James Hunter Ross" <james.ross@.oneilsoft.com> wrote in message
news:OYhK%23KdcFHA.3828@.tk2msftngp13.phx.gbl...
>A customer of ours was considering replication as a means of maintaining
>data in a second DB on a second server for reporting use only. We think
>replication is overkill since they won't mind if the data is a day or two
>old.
> I like the idea of simply restoring their most recent full backup on the
> reporting server, but I'm not sure if they do a full backup every night.
> What are other approaches that folks use to accomplish this sort of thing?
> Log shipping doesn't seem right; replication seems like overkill. DTS
> possibly? Any thoughts, links, or words will be greatly appreciated!
> Thanks in advance for your time,
> James Hunter Ross
>|||Keep it simple, if possible. Backup restore is as simple as it gets, and you
get your backups tested
each time.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"James Hunter Ross" <james.ross@.oneilsoft.com> wrote in message
news:OYhK%23KdcFHA.3828@.tk2msftngp13.phx.gbl...
>A customer of ours was considering replication as a means of maintaining da
ta in a second DB on a
>second server for reporting use only. We think replication is overkill sin
ce they won't mind if
>the data is a day or two old.
> I like the idea of simply restoring their most recent full backup on the r
eporting server, but I'm
> not sure if they do a full backup every night.
> What are other approaches that folks use to accomplish this sort of thing?
Log shipping doesn't
> seem right; replication seems like overkill. DTS possibly? Any thoughts,
links, or words will be
> greatly appreciated!
> Thanks in advance for your time,
> James Hunter Ross
>|||We use log shipping for this as our main DB is too large to restore nightly.
Works well.
Mike Kruchten
"James Hunter Ross" <james.ross@.oneilsoft.com> wrote in message
news:OYhK%23KdcFHA.3828@.tk2msftngp13.phx.gbl...
>A customer of ours was considering replication as a means of maintaining
>data in a second DB on a second server for reporting use only. We think
>replication is overkill since they won't mind if the data is a day or two
>old.
> I like the idea of simply restoring their most recent full backup on the
> reporting server, but I'm not sure if they do a full backup every night.
> What are other approaches that folks use to accomplish this sort of thing?
> Log shipping doesn't seem right; replication seems like overkill. DTS
> possibly? Any thoughts, links, or words will be greatly appreciated!
> Thanks in advance for your time,
> James Hunter Ross
>sql

Off-line replication

Is it possible with SQL Server 2000 to implement a replication offline
between 2 sites which would be connected sometimes using a modem. I
wonder how the replication can be done.
Thanks for advice
Its entirely possible. Check out
http://support.microsoft.com/default.aspx?scid=kb;[LN];241149
and
http://support.microsoft.com/default.aspx?scid=kb;[LN];105194
For more info.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"plo" <plochert@.club-internet.fr> wrote in message
news:355fd753.0409130335.363aa46b@.posting.google.c om...
> Is it possible with SQL Server 2000 to implement a replication offline
> between 2 sites which would be connected sometimes using a modem. I
> wonder how the replication can be done.
> Thanks for advice

Odd INSERT INTO issue with replication setup

I've got a db setup for replication. Replication works fine in both
directions. However ...
On the SQL2k backend, I can do an INSERT INTO to a particular table
(Results) with no problem. When I try to do the same INSERT INTO on the
Results table with SQLCE, I get the error message, "A duplicate value cannot
be inserted into a unique index". Note that I can do an UPDATE on the
Results table with no problem.
I do have one guidcol (uniqueidentifier, Non-null) on the SQL Server table.
To simplify matters, I have NO indexes (except the PK) and a single INT
primary key.
I've noticed in the Query Analyzer (SQLCE), that after a replication sync,
there are now 3 index (?) columns on the table, 2 of which are not in the
main SQLServer table.
s_Generation (int)
s_RowLineage (varbinary)
rowguid (uniqueidentifier)
Is this INSERT INTO failure somehow related to the extra columns added or is
this a rowguid problem?
Earl,
does your INSERT INTO specify the guid's value?
Rgds,
Paul Ibison
|||No it does not. My understanding is that this is a read-only column?
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eVEX24TVFHA.3044@.TK2MSFTNGP10.phx.gbl...
> Earl,
> does your INSERT INTO specify the guid's value?
> Rgds,
> Paul Ibison
>
|||If there's only one index on the PK and you're not entering a duplicate
record, then the problem must be with the system tables. I notice that you
have posted this same question some time ago without it being solved. Have
you reinitialized in the meantime? Does the error occur after
reinitialization? How about if you remove replication and set it up - is it
reproducible?
Rgds,
Paul Ibison
|||Yes, I actually removed replication from SQL2k, made sure everything was
cleaned out of the database and set it all back up (I drop the database
during the replication process on the subscriber/SQLCE side). I'm really
scratching my head on this one, because everything "looks" correct. I posted
the code for the INSERT INTO logic over in the
microsoft.public.dotnet.framework.adonet forum, just in case I missed
something on that side of it. Apparently it is accurate, as I've had no
responses to a request for input.
What is left? Does the SQLCE database not actually generate a guid for that
column?
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:eRws5BYVFHA.628@.TK2MSFTNGP09.phx.gbl...
> If there's only one index on the PK and you're not entering a duplicate
> record, then the problem must be with the system tables. I notice that you
> have posted this same question some time ago without it being solved. Have
> you reinitialized in the meantime? Does the error occur after
> reinitialization? How about if you remove replication and set it up - is
> it reproducible?
> Rgds,
> Paul Ibison
>

ODBCBCP Driver Mismatch

Hello,
I am receiving the following error message whenever I try to replicate using Snapshot repl. (or any type of replication) from the snapshot agent:
Error Message: The process could not bulk copy out of table '[dbo].[syncobj_xxxxxxxx]'.
Error Details: ODBCBCP/Driver version mismatch
(Source: ODBC SQL Server Driver (ODBC); Error number: 0)
I have checked the versions of the odbcbcp.dll on both of my SQL Servers (both of which are win2k3 w/ SQL Server 2000 sp3) and they are both 2000.85.1022.0. The version number of sqlsrv32.dll and sqlsrv32.rll are 2000.85.1025.0. Do all three have to mat
ch, is that my problem? Please HELP!! I can't replicate at all!
there are some reports that this problem can be solved by upgrading to a
consistent MDAC versions on both machines.
"Paul Pelletier" <anonymous@.discussions.microsoft.com> wrote in message
news:3E372B82-39B2-4A93-B7DE-5B7740527F13@.microsoft.com...
> Hello,
> I am receiving the following error message whenever I try to replicate
using Snapshot repl. (or any type of replication) from the snapshot agent:
> Error Message: The process could not bulk copy out of table
'[dbo].[syncobj_xxxxxxxx]'.
> Error Details: ODBCBCP/Driver version mismatch
> (Source: ODBC SQL Server Driver (ODBC); Error number: 0)
> I have checked the versions of the odbcbcp.dll on both of my SQL Servers
(both of which are win2k3 w/ SQL Server 2000 sp3) and they are both
2000.85.1022.0. The version number of sqlsrv32.dll and sqlsrv32.rll are
2000.85.1025.0. Do all three have to match, is that my problem? Please
HELP!! I can't replicate at all!
|||Hillary,
I have, I re-applied MDAC 2.7 on both SQL Servers and still the same problem. Any other possible solutions?
Do all there files have to have the same version numbers?
Thanks,
Paul
|||Check the version of the ODBC32.dll. It could be the one that is
mismatched. It should be version 3.525.1022.0.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||It is mismatched in a sense. The odbcbcp.dll is version 2000.85.1022.0. The sqlsrv32.dll is 2000.85.1025.0. The sqlsrv32.rll is 2000.85.1025.0. So really the one that is mismatched is the sqlsrv32.dll, but which version should be the correct version f
or all three, the 1025 or 1022?
Thanks again,
Paul
|||Sorry about the previous post, I did not completely read your post and I missed the fact that you were talking about a completely different dll, I'm a tard! Anyway both of the odbc32.dll do match on both machines and they are in fact 3.525.1022.0. Where
now?