thnx for enlightening me. m still a novice...

You can also check if the admin has reset the password or the password has expired for that instance through which you access SQL server.

You can also try the following:

use database_name

select * from sys.tables where type ='u'

and name like '%criteria%'

Thanks buddy...Will bug you if any probs...Can I have your Email ID?

Raj has got the right point. It seems I'll have to change my approach.

Thanks Guyzzz..

Thanks Adi & Raj for your responses.

Raj has been on the point. It seems I'll have to change my approach to acheive the same.

Thanks All for your valuable responses.

Could you please elaborate on the use of both...

Yeah you are right but the situation is such that the business users wont bother executing the stored procedure.

Changes at table level is not possible since the system would be...

Thanks Adi & Raj for the reply.

The situation is that the user will only execute the job. I wanted to know if there is some mechanism in sql server 2005...

EXEC master.dbo.sp_addlinkedserver @server = N'Linked_Server_Name', @srvproduct=N'server_to_link_name', @provider=N'SQLNCLI', @datasrc=N'server_to_link_name', @catalog=N'DatabaseName'

GO

EXEC master.dbo.sp_serveroption @server=N'Linked_Server_Name', @optname=N'collation compatible', @optvalue=N'true'

GO

EXEC master.dbo.sp_serveroption @server=N'Linked_Server_Name', @optname=N'data access', @optvalue=N'true'

GO

EXEC master.dbo.sp_serveroption @server=N'Linked_Server_Name', @optname=N'dist', @optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @server=N'Linked_Server_Name', @optname=N'pub', @optvalue=N'false'

GO

EXEC master.dbo.sp_serveroption @server=N'Linked_Server_Name', @optname=N'rpc',...

I wasn't able to find the exact cause. But what I did was:

1) I reconfigured the MSDTC.

2) I created a new linked server and used the linked server script...

I am using SQL Server 2000(80) as the compatibilty level for SQL 2005 database which is the same as in SQL 2000 database.

One important point I would like to...

Thanks Mike...

But I checked well all the date conversions where probably the code could crash down on different versions of SQL Server.

Also checked with the date settings on the servers.

Thnx...Its working...