Thanks.

This does the trick 🙂

Thanks for your responses.

The only thing is I want to replace the character(s) only if it occurs at the end so 'opobo' strip away 'o' should become 'opob'

/*

* You will find a very simple example of creating a folder and file via the sql clr below.

*

* please note the following:

*

* There...

alen teplitsky (10/13/2010)

---

i'm in the process of collecting performance data and creating reports about it. next up is i want to collect data every hour or so on how much...

Whats wrong with having it persisted to a file, bulk inserting it in the Stored Procedure to a temp./staging table and then copying them to any relevant tables?

I get an incorrect syntax near exec?

I think the placement of the "Exec"/"Dynamic Sql" statement is invalid.

You can always pre-fetch the rows you need with an Insert...Exec(your statement) into a...

Actually, now I think about it you could probably schedule it with Sql Agent and start it with sp_start_job.

All this being said, I can't say any issues you may run...

Use the dtexecui to build the execute package command.

Copy the command to your Stored Procecure, executing it with xp_CmdShell (or a CLR Procedure).

Since no test data, I have no easy way to test if this approach might work.

You could probably include a Row_Number column partitioned/ordered by the appropriate column then

simply use a...

I think you might want to respond to Lutz's side note? Is the ClientId Column Indexed appropriately?

I would have thought Lynn's suggestion would have worked for you?

"Msg 1934, Level 16, State 1, Procedure PROC_adddistributors, Line 12

SELECT failed because the following SET options have incorrect settings: 'ANSI_NULLS, QUOTED_IDENTIFIER'. Verify that SET options are correct for use with...

hmmm... what you didn't actually point out initially is that the code is part of a Stored Procedure, yes?

Try this:

Do a select from sys.sql_modules and identify your procedure.

on that row...

You can check the SET options for the current connection with "DBCC UserOptions"

If your sole aim is to return Distinct ContactId's then introducing a Distinct or Group By clause should

fix it but you may want to go over what it is you...