What is the error message you are getting, or is it possible for you to post some of your procedure code?

David,

Good info on the OPENQUERY stuff; wasn't aware of that.

Hunta,

I would tend to lean more towards David's suggestion of...

Could be a permissions issue. Does the executing user have appropriate permissions to the table on the linked server?

Specifically, what do you mean by "working of SQL Server". If you are talking about the internals of SQL's storage and retrieval engine, or the query optimizer internals, I...

quote:

---

jpipes,

My actual query has other combinations in the where clause . This stored proc will come in handy another time.Thank You.

The original...

Take the old stuff out and into an OLAP or mixed OLTP/OLAP database. It should speed things up a little, but only if the active user transactions are mixed...

Or, don't bother with any of the conversion stuff and just:

CREATE PROC dbo.GetProjects

  @StartDate SMALLDATETIME

, @EndDate   SMALLDATETIME

AS

BEGIN

SELECT Fields -- Don't use * !!!

FROM...

I actually like the MySQL INSERT INTO ... ON DUPLICATE KEY UPDATE syntax. Very clear and easy to understand.

http://www.mysql.com/doc/en/INSERT.html

no problemo. just a script I thought of this morning...worked great (surprisingly...)

--

Cheers

OR, another way, just to show you examples...

CREATE TABLE #temp (OutputText NVARCHAR(1000))

--

INSERT INTO #temp

EXEC sp_executesql N'exec master.dbo.xp_cmdshell ''dir c:\MSSQL7\Binn'''

--

SELECT RIGHT(OutputText, CHARINDEX(' ', REVERSE(OutputText))) FROM #temp

WHERE PATINDEX('%<DIR>%',...

EXEC master.dbo.xp_cmdshell 'dir c:\MSSQL7'

Of course, replace c:\MSSSQL7 with whatever directory on the server you want...

Did you find anything in the SQL Server logs, or in the Event Viewer -> Applications log? Specifically, looking for something like 'Bypassing recovery for database 'msdb'...marked as Suspect'?

...