Are you using instance name of SQL Server 2005 along with IP. And what message do you get as failure message?

Think about some recent backup.

Grow gradually with practice and learning side by side. No short cuts.

You may visit following address with basic details for linked sql server instances

http://www.databasejournal.com/features/mssql/article.php/3691721/Setting-up-a-Linked-Server-for-a-Remote-SQL-Server-Instance.htm

Thanks , and just want to confirm that we may not get last modification date in sql server 2000?

Regards

Thanks, its good.

In SQL Server 2000 system meta data was stored in tables. e.g. sysobjects. In SQL Server 2005 meta data is now provided through views like sys.objects. For sake of compatibility...

Ok, that was a valid reason. Name is changed for this table with addition of some suffixes in tempDB. Now please let me know if there are any privileges required...

You can use any of both options for user databases. Once you get database in SQL Server 2005 then check its compatibility and set it to 90 for complete SQL...

I have changed the flow little bit and modified the privileges. User is able to create temp table without any problem. Now, I have to get columns of temp table...

Yes, off course temp table is being created with # sign. So do you have any idea of some other reason.

Regards

But without adding the user in DDLAdmin role, it was not able to create temp table. Is there any further requirement to allow it to create temp table?

Regards

Thanks for solution.

Please specify some reference for details of this behavior.

Regards

None of the given options can be used to memory , processor affinity etc. So there should be no confusion to choose the applied option.

Regards

Thanks , with little more modification , it will work for me.

Regards