As I said earlier, before executing the query

replace all [ with [[]

Do not replace ] with []]. Keep them as it is.

For your example

"a[k']p" ...

Transact Sql help says that

LIKE ']' to be used for searching for ] character and not '[]]'.

Hope this helps

This may not be due to corruption of index.

This might be due to the fact that the statistics have not been updated on the index.

Sql*Server maintains statistics on each...

This means that your sql server is Case Sensitive, Accent Sensitve.

More details available at following msdn site

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_ca-co_5ell.asp

COL_NAME can be used to retrieve the column names of temporary tables using following syntax.

USE TEMPDB

SELECT COL_NAME(object_id("tempdb..#temp_table"),2)

where #temp_table is the name of temporary table. The above sql returns 2nd column...

Sorry. Jeremy has already posted the aswer. Mine was a repeat (and an error as well missing mkdir). Please ignore,

You can use sql similar to the following to create a directory dynamically.

DECLARE @m_date VARCHAR(255)

DECLARE @m_cmd VARCHAR(255)

SET @m_date = CAST(DAY(GETDATE()) AS VARCHAR) + DATENAME(m,GETDATE())+ CAST(YEAR(GETDATE()) AS VARCHAR)

SET @m_cmd ...

one alternative is to use OSQL command line utility. See books online for more details on this command.

Can you please give the error details displayed.

Thanks

I have created a sample for you.

Assuming there is a SP in database test_sp which takes an input parameter @p_id and returns a recrodset.

-------------------------------------------

'Create ado command object

...

First create a AdoCommandObject for the stored procedure.

Create the parameters for SP.

Set the values to parameters

Use adoCommandObject.Execute method to get the recordset.

mahgoub, you are most welcome. I am glad it helped

The error is because @ExecSP has been declared as VARCHAR. Change the declaration to NVARCHAR.

sp_executesql can take only NVARCHAR data as parameter

Try the following

SET @ExecSP = 'EXEC ' + @DBName + '.dbo.stp_Interface_Import_ReportData 1'

Execute sp_executesql @ExecSP

I agree with Darren. If it is possible to create ancestry list column easily then this is certainly better idea as this involves less number of selects compared to other...