MSSQL 2000: How can we track table/sp/function changes?

My company would like to start keeping track of everytime a table, stored procedure, or function is changed.
What is the best way to do this?Option 1)
Create a database for storing metadata on all the other databases. Nightly, run a query that loops across all database and records all the objects along with their checksum values, and notes any objects who's checksum value has changed.

Option 2)
Upgrade to SQL Server 2005 and create database triggers to log changes to objects.|||sourcegears vault, visual sourcesafe. nothing makes it into our software\database builds that is not in our sourcecode management software.|||Revoke sysadmin/DBO rights from everyone but the DBAs.|||As suggested you cna take help of Visual Sourcesafe or PVCS in order to take care of object changes.

mssql 2000 update from select

I am trying to update a table from a select statement, any suggestions?

update (select column1 from table1)
set column2 = 'value'

The data in column1 contains the name of the table I want to update column2 with the 'value'.

I'm am pretty sure the syntax is in correct along with the structure. The error...

Server: Msg 170, Level 15, State 1, Line 2
Line 2: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 3
Line 3: Incorrect syntax near '='.

Quote:

Originally Posted by tdority

I am trying to update a table from a select statement, any suggestions?

update (select column1 from table1)
set column2 = 'value'

The data in column1 contains the name of the table I want to update column2 with the 'value'.

I'm am pretty sure the syntax is in correct along with the structure. The error...

Server: Msg 170, Level 15, State 1, Line 2
Line 2: Incorrect syntax near '('.
Server: Msg 170, Level 15, State 1, Line 3
Line 3: Incorrect syntax near '='.

nope, the syntax is not correct. in this case you have to build the string for the entire update command..

set @.sqlcmd = 'update ..."

exec (@.sqlcmd)|||Please explain how to build.

MSSQL

I have created a tool using vb.net,with mssql as backend.i need to
create the database and the table in the database using some scripts or
what ever relevent methods.How can we make the database while
installing the software.you could call the following from VB.NET:
osql.exe -Usa -Ppassword -i d:\dbr\create_database_script.sql -n
-oD:\DBR\OUTPUT\SQL_SCRIPT_LOGS\outputfile.txt
--
--
Sasan Saidi
Senior DBA
MSc in CS, MCSE4, IBM Certified MQ 5.3 Administrator
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Armagadone" wrote:
> I have created a tool using vb.net,with mssql as backend.i need to
> create the database and the table in the database using some scripts or
> what ever relevent methods.How can we make the database while
> installing the software.
>

MSSQL

I have created a tool using vb.net,with mssql as backend.i need to
create the database and the table in the database using some scripts or
what ever relevent methods.How can we make the database while
installing the software.
you could call the following from VB.NET:
osql.exe -Usa -Ppassword -i d:\dbr\create_database_script.sql -n
-oD:\DBR\OUTPUT\SQL_SCRIPT_LOGS\outputfile.txt
--
Sasan Saidi
Senior DBA
MSc in CS, MCSE4, IBM Certified MQ 5.3 Administrator
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Armagadone" wrote:

> I have created a tool using vb.net,with mssql as backend.i need to
> create the database and the table in the database using some scripts or
> what ever relevent methods.How can we make the database while
> installing the software.
>

Mssql

create table ename (cid bigint,cname varchar(20),yoe bigint,domain varchar(20),special varchar(20),location varchar(20),age bigint,rsta varchar(20),percentage bigint,record varchar(20))

select cid,cname,yoe,domain,special from ename where (cid=23 and cname='Tamil' and yoe=2 and domain ='it' and special='computer' and location='chennai' and record='dotnet') or (age='' and rsta='' and percentage='')

Quote:

Originally Posted by thamilarasangc

create table ename (cid bigint,cname varchar(20),yoe bigint,domain varchar(20),special varchar(20),location varchar(20),age bigint,rsta varchar(20),percentage bigint,record varchar(20))

select cid,cname,yoe,domain,special from ename where (cid=23 and cname='Tamil' and yoe=2 and domain ='it' and special='computer' and location='chennai' and record='dotnet') or (age='' and rsta='' and percentage='')

create table ename (cid bigint,cname varchar(20),yoe bigint,domain varchar(20),special varchar(20),location varchar(20),age bigint,rsta varchar(20),percentage bigint,record varchar(20))

select cid,cname,yoe,domain,special from ename where ((cid=23 and cname='Tamil' and yoe=2 and domain ='it' and special='computer' and location='chennai' and record='dotnet') or (age='' or rsta='' or percentage=''))

MSSQL

I have created a tool using vb.net,with mssql as backend.i need to
create the database and the table in the database using some scripts or
what ever relevent methods.How can we make the database while
installing the software.you could call the following from VB.NET:
osql.exe -Usa -Ppassword -i d:\dbr\create_database_script.sql -n
- oD:\DBR\OUTPUT\SQL_SCRIPT_LOGS\outputfil
e.txt
--
Sasan Saidi
Senior DBA
MSc in CS, MCSE4, IBM Certified MQ 5.3 Administrator
"I saw it work in a cartoon once so I am pretty sure I can do it."
"Armagadone" wrote:

> I have created a tool using vb.net,with mssql as backend.i need to
> create the database and the table in the database using some scripts or
> what ever relevent methods.How can we make the database while
> installing the software.
>

msreplication_queue table growing on subscriber - why

Have a live and standby server and failed over to the standby after (i
thought) using EM to turn off replication.
Now find out that the ms_replication_table on the subscriber is growing -
what have I missed ?
The very least I need to do is remove/delete this table as I now don't have
enough disk space for a backup and currently no tape drive
Suggestions please
Thanks
Luci
I suppose the question is "do you need to send this data back to the
publisher?". If so, then running the queue reader agent will prepare the
table for truncation. If you aren't interested in this data, then you'll need
to drop the subscription. If the publisher is no longer available, then you
can use sp_removedbreplication to remove this table and any other remnants of
replication.
Cheers,
Paul Ibison
|||Thanks for quick reply Paul.
No we don't need this data (we're not replicating at the moment) not
even sure where its coming from as the original live is not in use !
Tried running sp_removedbreplication on the subscriber yesterday but the
transaction log just doubled ( and we have no space).
To stop it growing then, do I just go on the original publisher and just
drop the subscription - presume thats a an option in EM ? or do I have to run
a stored procedure on there ?
Cheers
Luci
"Paul Ibison" wrote:

> I suppose the question is "do you need to send this data back to the
> publisher?". If so, then running the queue reader agent will prepare the
> table for truncation. If you aren't interested in this data, then you'll need
> to drop the subscription. If the publisher is no longer available, then you
> can use sp_removedbreplication to remove this table and any other remnants of
> replication.
> Cheers,
> Paul Ibison
|||Hi Luci,
I was suggesting sp_removedbreplication for the case where the publisher was
not available, but this should still be ok. If you run sp_dropesubscription
on the publisher we should be back to normal. The balooning of the
transaction log on the subscriber is normal when you are deleting so much
data. You might want to backup the log and then shrink it, or if the log is
not required for the backup strategy, you could use simple recovery mode and
then shring the log file.
HTH,
Paul Ibison
|||Thanks again Paul
Plan to do this tonight out of hours tonight, going with your second
suggestion by
putting db in simple mode and trying sp_removedbreplication on the
subscriber first.
Cheers
Luci
PS Glad you answered as I found this forum through your replicationanswers
website Thank you again !
"Paul Ibison" wrote:

> Hi Luci,
> I was suggesting sp_removedbreplication for the case where the publisher was
> not available, but this should still be ok. If you run sp_dropesubscription
> on the publisher we should be back to normal. The balooning of the
> transaction log on the subscriber is normal when you are deleting so much
> data. You might want to backup the log and then shrink it, or if the log is
> not required for the backup strategy, you could use simple recovery mode and
> then shring the log file.
> HTH,
> Paul Ibison
>
|||What I'd probably try is to delete the queue records in batches. The batch
size could be 10000 and each time round the loop you backup the log with
truncate_only set. this way the records will get removed without balooning
the log, and you can drop the subscription at the end...
HTH,
Paul Ibison
|||Hi
Just to let you know we got there in the end.
Ended up truncating the msreplication_queue_table, then tried
sp_removedbreplication again which failed as it couldn't drop tables and the
tempdb couldn't extend. So, manually dropped the tables in question, after
which
the sp_removedbreplication did work. Thank you for your help. Cheers Luci
"Paul Ibison" wrote:

> What I'd probably try is to delete the queue records in batches. The batch
> size could be 10000 and each time round the loop you backup the log with
> truncate_only set. this way the records will get removed without balooning
> the log, and you can drop the subscription at the end...
> HTH,
> Paul Ibison
>

MSreplication_queue getting dropped in SQL 2005

I have set up an Updateable Subscriber replication between databases A and B.
This creates and uses the MSreplication_queue system table in the destination
(B) database.
I have lot of other tables being replicated from A to B, all standard
Transactional replication. e.g. Table C is replication from A to B,
transaction replication. When I dropped the publication for table C from A,
it dropped the following objects in B as well:
MSreplication_queue
MSrepl_queuedtraninfo
This caused the Updateable Subscription to fail. I got around this by
creating another (dummy) Updateable Subscriber replication which recreated
the above tables, and then dropped the dummy publication.
This sounds like a serious bug, because why would dropping a simple
transactional replication drop these two tables, especially since dropping an
UPDATEABLE SUBSCRIBER replication doesn't touch these tables AND a
transactional publication has nothing to do with these tables ?
We did not experience this problem in SQL 2000.
Has anyone else come across this problem ? Is there a fix for it, as it's
causes a serious problem is our organisation because a critical process
depends on the updateable subsciption working.
Yes this seems to be an issue with the way the subscription is dropped,
please open a case with PSS so that we can look into this
"Pranil" wrote:

> I have set up an Updateable Subscriber replication between databases A and B.
> This creates and uses the MSreplication_queue system table in the destination
> (B) database.
> I have lot of other tables being replicated from A to B, all standard
> Transactional replication. e.g. Table C is replication from A to B,
> transaction replication. When I dropped the publication for table C from A,
> it dropped the following objects in B as well:
> MSreplication_queue
> MSrepl_queuedtraninfo
> This caused the Updateable Subscription to fail. I got around this by
> creating another (dummy) Updateable Subscriber replication which recreated
> the above tables, and then dropped the dummy publication.
> This sounds like a serious bug, because why would dropping a simple
> transactional replication drop these two tables, especially since dropping an
> UPDATEABLE SUBSCRIBER replication doesn't touch these tables AND a
> transactional publication has nothing to do with these tables ?
> We did not experience this problem in SQL 2000.
> Has anyone else come across this problem ? Is there a fix for it, as it's
> causes a serious problem is our organisation because a critical process
> depends on the updateable subsciption working.

MSreplication_agent_status in sql server 2005

Is this table still residing in tempdb in 2005? I have created replication but the server doesn't have this table anymore

No, replication does not use this table anymore in SQL 2005.|||

Thanks greg..

Any idea how/why it was used before? why it's not used in 2005? Any articles on this would be much appreciated

|||There was a redesign that eliminated the need for this table.

msrepl_tran_version

Hi all,
I've just noticed that a new column has been added to a table entitled ''msrepl_tran_version'. Anyone know why this might be?
I'm using sql 2000.
Many thanks
Sam
This column is used by replication. Is this table participating in
replication (updatable subscriptions)?
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:EEC90423-EBA6-4423-B68E-750FBD8D5CFA@.microsoft.com...
> Hi all,
> I've just noticed that a new column has been added to a table
entitled ''msrepl_tran_version'. Anyone know why this might be?
> I'm using sql 2000.
> Many thanks
> Sam
>

msrepl_tran_version

Hi all,
I've just noticed that a new column has been added to a table entitled ''msr
epl_tran_version'. Anyone know why this might be?
I'm using sql 2000.
Many thanks
SamThis column is used by replication. Is this table participating in
replication (updatable subscriptions)?
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:EEC90423-EBA6-4423-B68E-750FBD8D5CFA@.microsoft.com...
> Hi all,
> I've just noticed that a new column has been added to a table
entitled ''msrepl_tran_version'. Anyone know why this might be?
> I'm using sql 2000.
> Many thanks
> Sam
>

msrepl_tran_version

Hi all,
I've just noticed that a new column has been added to a table entitled ''msrepl_tran_version'. Anyone know why this might be?
I'm using sql 2000.
Many thanks
SamThis column is used by replication. Is this table participating in
replication (updatable subscriptions)?
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:EEC90423-EBA6-4423-B68E-750FBD8D5CFA@.microsoft.com...
> Hi all,
> I've just noticed that a new column has been added to a table
entitled ''msrepl_tran_version'. Anyone know why this might be?
> I'm using sql 2000.
> Many thanks
> Sam
>

MSrepl_identity_range in publisher and distribution DBs

Can anyone shed any light on why this table exists in both the publication DB AND the distribution DB. The reference material just says:

The MSrepl_identity_range table provides identity range management support. This table is stored in the publication, distribution and subscription databases

However,doesn't shed any light on WHY it is in each database.

For merge replication which one should I be looking at to determine the next seed value?

Assuming I am looking at the appropriate records in the distribution db (where publication_db = my publication db) should the values be identical to the values in the MSrepl_identity_range table in the publication db?

Ok.

It looks to me as if the table in the publication database serves no useful purpose.

The next_seed value in the distribution table is updated to reflect the starting point for the next range (regardless of whether it is the publisher or a subscriber that is being allocated a new range) While the next_seed value in the publication database never changes...

|||

In the publication database it is for the range assigned to table which could be in other publications.

The one in the distribution database is used as a point of reference when assigning new ranges to subscribers. This is done to ensure that the range is never assigned to two nodes in your replication topology.

Did you review this article?

http://www.simple-talk.com/sql/database-administration/the-identity-crisis-in-replication/

|||

Thanks.

I'm still not clear on what purpose the table in the publication database serves since it doesn't appear to ever be updated. The table in the distribution database keeps track of the last_seed value. I'm assuming that the tabvle in the publication db would be used for a different type of replication (transactional replication perhaps?)

As a work-around I created a script that re-seeds the identity in the publication database (to a value that should be greater than any record created on any existing subscriber) and adjusts the next_seed value to reflect this (by calling sp_adjustpublisheridentityrange). When each subscriber next synchronises they will follow that up with a re-initialisation (so they get assigned a new range starting from my new next_seed value. Once all subscribers have been re-initialised we shouldn't get any more clashes.

This workaround is purely to avoid having to bring all of the remote subscribers back in at the same time : the 'ideal' fix I think would be to synch all subscribers, drop the publication, reseed the identity on the publisher, re-create the publication and initialise all subscribers. It's just that this is a major disruption to the subscribers (who are spread out over a large geographic region).

sql

MSREPL_Commands TABLE

I don't think I ever resolved this issue & now I am quite concerned about my growing MSRepl_Commands table.
It has over 9 million rows.
What steps can I take to reduce the number of rows in this table?
Thanx!
JUDE
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
"Jude" <judes@.email.uophx.edu> wrote in message news:utbKUSEtHHA.2752@.TK2MSFTNGP06.phx.gbl...
I don't think I ever resolved this issue & now I am quite concerned about my growing MSRepl_Commands table.
It has over 9 million rows.
What steps can I take to reduce the number of rows in this table?
Thanx!
JUDE
|||Expect this if you have anonymous subscribers. If this is a problem for you
consider using named subscribers if you can.
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
"Jude" <judes@.email.uophx.edu> wrote in message
news:utbKUSEtHHA.2752@.TK2MSFTNGP06.phx.gbl...
I don't think I ever resolved this issue & now I am quite concerned about my
growing MSRepl_Commands table.
It has over 9 million rows.
What steps can I take to reduce the number of rows in this table?
Thanx!
JUDE

MSREPL_COMMANDS Question

How does one purge the Msrepl_commands table in the Distribution
database? My table has 3447147 rows & I think this is excessive. Any
suggestions?
query MSDistribution_status in your distribution database - this will help
you to understand where the problem is
Otherwise run the distribution clean up agent.
Hilary Cotter
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
<jlshoop@.hotmail.com> wrote in message
news:1129691264.949911.252410@.z14g2000cwz.googlegr oups.com...
> How does one purge the Msrepl_commands table in the Distribution
> database? My table has 3447147 rows & I think this is excessive. Any
> suggestions?
>

MSrepl_commands question

Hi,
I have 750,000 commands in the table MSrepl_commands. The
cleanup agent hasn't removed them, although they have all
gone to my one subscriber, and I don't have anonymous
subscribers. What am I missing??
Rgds,
BB
You should be able to delete them manually. You will have to delete them
from the msrepl_transactions and msrepl_commands tables.
Before you do this, I would try to run the clean up manually.
EXEC dbo.sp_MSdistribution_cleanup @.min_distretention = 0,
@.max_distretention = 0
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"BB" <anonymous@.discussions.microsoft.com> wrote in message
news:2a4401c4a54e$21714500$a501280a@.phx.gbl...
> Hi,
> I have 750,000 commands in the table MSrepl_commands. The
> cleanup agent hasn't removed them, although they have all
> gone to my one subscriber, and I don't have anonymous
> subscribers. What am I missing??
> Rgds,
> BB
|||Thanks Hilary,
running
EXEC dbo.sp_MSdistribution_cleanup @.min_distretention =
0, @.max_distretention = 0
has me worried - what if another command comes in just
before I run it - presumably it will be deleted?
Also, have you ever seen this behaviour before - ie
commands retained in this table? Any idea what causes it?
Thanks,
BB
|||only commands that are replicated to the subscriber will be deleted.
Undistributed commands will not.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"BB" <anonymous@.discussions.microsoft.com> wrote in message
news:43d401c4a55b$1749b550$a401280a@.phx.gbl...
> Thanks Hilary,
> running
> EXEC dbo.sp_MSdistribution_cleanup @.min_distretention =
> 0, @.max_distretention = 0
> has me worried - what if another command comes in just
> before I run it - presumably it will be deleted?
> Also, have you ever seen this behaviour before - ie
> commands retained in this table? Any idea what causes it?
> Thanks,
> BB
>
|||btw you can always pipe the msrepl_commands and msrepl_transaction tables to
backup tables before you do the deletes or manually run the clean up
command.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"BB" <anonymous@.discussions.microsoft.com> wrote in message
news:43d401c4a55b$1749b550$a401280a@.phx.gbl...
> Thanks Hilary,
> running
> EXEC dbo.sp_MSdistribution_cleanup @.min_distretention =
> 0, @.max_distretention = 0
> has me worried - what if another command comes in just
> before I run it - presumably it will be deleted?
> Also, have you ever seen this behaviour before - ie
> commands retained in this table? Any idea what causes it?
> Thanks,
> BB
>
|||Thanks Hilary - any idea why it happens?
TIA,
BB
|||Sometimes the distribution clean up agent gets locked and is picked as the
dead lock victim. This normally leads to even more locking as the cleanup
agent has to do more work. You can try to run your distribution agent at a
greater frequency, ie every minute, or stop your log reader and distribution
agent and then run it.
On high volume systems when you constantly get this type or error you might
consider a remote distributor.
"BB" <anonymous@.discussions.microsoft.com> wrote in message
news:2bed01c4a564$10f7bb80$a501280a@.phx.gbl...
> Thanks Hilary - any idea why it happens?
> TIA,
> BB
|||I think you would be best to use a maxium_retention period of 24. Paul
Ibison pointed out to me that a value of 0 will remove undistributed
transactions.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"BB" <anonymous@.discussions.microsoft.com> wrote in message
news:43d401c4a55b$1749b550$a401280a@.phx.gbl...
> Thanks Hilary,
> running
> EXEC dbo.sp_MSdistribution_cleanup @.min_distretention =
> 0, @.max_distretention = 0
> has me worried - what if another command comes in just
> before I run it - presumably it will be deleted?
> Also, have you ever seen this behaviour before - ie
> commands retained in this table? Any idea what causes it?
> Thanks,
> BB
>
sql

MSOLAP Error. Please help!

I have an Openrowset query, which connects to a cube and obtains the data in a table. This is run every day. This process has been running for over a year but now all of a sudden doesn't work and gives the erros mentioned below. When I reduce the records to be returned to about 1/4, then it runs fine else not. We are using Enterprise Version. Any help will be really appreciated.

Error when tried once -

OLE DB provider 'MSOLAP' reported an error. The provider ran out of memory.
[OLE/DB provider returned message: An error occurred during attempt to get a cell value.]
[OLE/DB provider returned message: The operation has failed because of an error in the COM component - unknown error ]
OLE DB error trace [OLE/DB Provider 'MSOLAP' IRowset::GetNextRows returned 0x8007000e: The provider ran out of memory.].

The second time I received -

ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 77 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
[OLE/DB provider returned message: An unexpected internal error has occurred.] [Microsoft][ODBC SQL Server Driver]Function sequence error

Thanks,
SauravRevisiting archived thread here: http://www.dbforums.com/archive/index.php/t-534601.html

MSmerge_tombstone growing and growing

I have merge replication setup up for 6 SQLCE Subscribers.
I have noticed that the MSmerge_tombstone table is growing
at a fast rate regardless of any changes to the data in
the database. It seems to be consistantly adding 50 rows
of data to the table every 2 minutes. As the table grows
it causes the SQLCE subscirbers to fail with the following
message:

ERROR: -2147467259
SQL Server Reconciler failed: Run

ERROR: -2147200925
: Failed to enumerate changes in the filtered
articles.

ERROR: 0
: {call sp_MSsetupbelongs
(?,?,?,?,?,0,?,?,1,?,?,?,?,?,?)}

ERROR: 0
: The merge process timed out while executing a
query. Reconfigure the QueryTimeout parameter and retry
the operation.

I'm sure that this is due to the size of the
MSmerge_tombstone.

Should the MSmerge_tombstone table grow at this rate?
36,000 rows every 24hrs!

I understand there is the sp_mergecleanupmetadata Stored
procedure but if i use this does that mean that because i
have to reinitialise all the subscribers, they are going
to have to pull down the whole subscription again.

I have since Changed a settings to make subscription
expiration date to 8 days instead of never expires but
we're still getting 50 rows added every 2 minutes

SQL SERVER 2000 SP3
Hope someone can shed some light on this for me.

Thanks.
.What is the level of service pack on SQL & SQL CE?
What is the value set for retention period of the publication?|||Satya,

SQL Server is SP3
SQL CE is just SQLCE1.0 devices running PPC2002

The subscription expiration was set to never expire, however this morning i have changed to publication properties to 8 days. I haven't reinitialised anything after this change.|||May try with reintialization and see whether error persists.

Have you tried sp_mergecleanupmetadata to clean up the data?|||I did try this sp last week when the table had grown to just under 1 million rows, however I was forced to reinitialise the subscriptions.

I will probably run it agian at the end of play today and then get them to resync in the morning. And then see if the change in retention has done anything.

running the sp and reinitialising on a regular basis is going to be difficult as the devices are synchronising throughout the day and I can't get them all in to upload their changes first. Plus I don't want them to download the whole subscription again. 5mb over a fairly slow link to the server.

Do you think 50 rows every 2 minutes is unusual behaviour. Or is this to be expected?

Thanks,

Tim|||On the terms of speed 50rows every 2 min. is no issue, as CE devices are meant to be slower as compared to Desktops/servers.

And may try contacting MS PSS to get hold of QFE build number 765 to fix the issue.

msmerge_tombstone error

Hi everyone.Is there any one who could help me on this error which i
encountered when i manually delete some records on user table in my
database.I cannot delete records,the error indicates:
cannot insert duplicate key in row in object 'msmerge_tombstone' with unique
index 'uc1msmerge_tombstone'.
Someone help on this.
Thank you
Pheter Flores
On Dec 13, 1:29 pm, MICS <M...@.discussions.microsoft.com> wrote:
> Hi everyone.Is there any one who could help me on this error which i
> encountered when i manually delete some records on user table in my
> database.I cannot delete records,the error indicates:
> cannot insert duplicate key in row in object 'msmerge_tombstone' with unique
> index 'uc1msmerge_tombstone'.
> Someone help on this.
> Thank you
> Pheter Flores
Check if there is any trigger on Delete action
|||This must be about Replication. You may get a better answer if you send this
post to Replication NG.
Ekrem ?nsoy
"MICS" <MICS@.discussions.microsoft.com> wrote in message
news:CE9D159A-FC62-4A82-BDCD-CD60D2679709@.microsoft.com...
> Hi everyone.Is there any one who could help me on this error which i
> encountered when i manually delete some records on user table in my
> database.I cannot delete records,the error indicates:
> cannot insert duplicate key in row in object 'msmerge_tombstone' with
> unique
> index 'uc1msmerge_tombstone'.
> Someone help on this.
> Thank you
>
> Pheter Flores
sql

msmerge_tombstone error

Hi everyone.Is there any one who could help me on this error which i
encountered when i manually delete some records on user table in my
database.I cannot delete records,the error indicates:
cannot insert duplicate key in row in object 'msmerge_tombstone' with unique
index 'uc1msmerge_tombstone'.
Someone help on this.
Thank you
Pheter FloresOn Dec 13, 1:29 pm, MICS <M...@.discussions.microsoft.com> wrote:
> Hi everyone.Is there any one who could help me on this error which i
> encountered when i manually delete some records on user table in my
> database.I cannot delete records,the error indicates:
> cannot insert duplicate key in row in object 'msmerge_tombstone' with unique
> index 'uc1msmerge_tombstone'.
> Someone help on this.
> Thank you
> Pheter Flores
Check if there is any trigger on Delete action|||This must be about Replication. You may get a better answer if you send this
post to Replication NG.
--
Ekrem Ã?nsoy
"MICS" <MICS@.discussions.microsoft.com> wrote in message
news:CE9D159A-FC62-4A82-BDCD-CD60D2679709@.microsoft.com...
> Hi everyone.Is there any one who could help me on this error which i
> encountered when i manually delete some records on user table in my
> database.I cannot delete records,the error indicates:
> cannot insert duplicate key in row in object 'msmerge_tombstone' with
> unique
> index 'uc1msmerge_tombstone'.
> Someone help on this.
> Thank you
>
> Pheter Flores