Does this need to be totally automated?  What are your rights on the sql server?

1. You said you have Enterprise Manager.  Using EM you can export the table into Access. ...

what's the specific error?

Check the BOL for string functions

Here you go:

declare

@Found Integer,

@Results varchar(100),

@sStr varchar(100)

set @sStr = 'Blue,Red,Green,Yellow,END'

while Len(@sStr) > 4

begin

     set @Found = patindex('%,%',@sstr)

     set @Results = left(@sstr,@Found-1)

     print isnull(@Results,'<null>')

     set @sStr =...

I've had no activity for hours and not had a "suspect" message.  We run merge replication with "continuous" synchronization.  We are also running merge replication with synchronization set at 20...

I'm not sure if this will work.  I don't think so, because

of the default instance being the servername.

sp_dropserver 'OLD_NAME' 

sp_adserver 'NEW_NAME', 'local'

We also conducted reseach as to where the best place to store images/documents.  Our orignal plan was to store the images in the file system and use Availl to replicate...

"exec sp_MSForEachTable 'GRANT SELECT ON ? TO MySQLUser'"

How would you NOT grant permissions using this sproc?  This undocumented sproc will grant select on every table, including sys tables.

I think Rob also...

Sorry about that Icon that was inserted; please ignore.  I don't recall clicking on any of those things.

We created this sproc to run about every 10 minutes in the development environment.  We have naming standards so this will work for us.  We only are granting "select" on...

You're inserting every record into the R713_SUM table.  Is this what you want to do?  This could take a while as the transaction log is mostly likely growing during this...

sstankus1,

Your technique is exactly what I was looking for, thanks.

Steve

Using row-level filtering will not help in this situation.  It's mainly used to only replicate rows which meet a certain criteria.

I'm also trying to accomplish the same thing.  Due to network interruptions, our replication will stop after n number of retries.  While I'm looking to the cause of the problem...

I'll give it a try.  Thanks

The Level 16 errors seem to be the toughest to trap within nested stored procedures because when they occur your procedure immediately exists to the calling procedure or program.  Other...