Look at the charindex function, you can use it to determine the position of the @, then use the left function to pull off the characters before it.

Andy

http://www.sqlservercentral.com/columnists/awarren/

Dont think it will work directly. Probably better off rolling your own replication code if you need this.

Andy

http://www.sqlservercentral.com/columnists/awarren/

No idea. Looks like you're running into a few compatibility issues. Tried a search on MSDN or google to see if you can maybe find a list? Would be interesting...

Close, but I think you are doing more work than you need. Then again, I read C# about as well as I read Klingon. Here is similar code for VB6.

dim...

Here is another way:

SELECT a.*

FROM OPENROWSET('SQLOLEDB','yourserver;'sa';'sapassword',

'exec Northwind.dbo.salesbycategory ''beverages''') AS a

GO

Andy

http://www.sqlservercentral.com/columnists/awarren/

Think your counter must be off. Tried using for/each?

Andy

http://www.sqlservercentral.com/columnists/awarren/

If its a single value you'd normally design the proc to return an output parameter. I think you can do a hack using openrowset if you want to treat it...

One option is to put triggers on all the tables. Several tools available that will do it for you, not that hard to roll your own if it needs to...

Try this:

select @@servername

Andy

http://www.sqlservercentral.com/columnists/awarren/

Have you considered using an identity col, or using a uniqueidentifier?

Andy

http://www.sqlservercentral.com/columnists/awarren/

Is there a foreign key on the table? Email me the entire trace if you have time (as text), I'll look some more.

Andy

http://www.sqlservercentral.com/columnists/awarren/

Thats a good question! Dont know that you can. I can see where having the option in the wizard would be nice, though I prefer to use separate files for...

Maybe force it to recompile each time?

Andy

http://www.sqlservercentral.com/columnists/awarren/

Please dont cross post. See this thread:

http://www.sqlservercentral.com/forum/topic.asp?TOPIC_ID=6710&FORUM_ID=65&CAT_ID=1&Topic_Title=System+Resource+Exceeded&Forum_Title=Performance+Tuning

Andy

http://www.sqlservercentral.com/columnists/awarren/

How big is the file you're trying to open? Maybe SQL cant allocate enough memory? How about compiling an exe and running from a job? Or just instantiating the dll...