Make sure you have all the login scripts as well as you will lose login maping after restoring the DB.

What is your exact requirment?

It's possible that while your table was in replication the identity got replicated & now after you remove the replication the identity is out of replicated but started from same...

This will give me all the sp's along with system sp's. I want only sp's created by user's.

Thanks for the reply.

When you put identity tables in replication you should create the table with including following command

 [IDENTITY [(seed, increment) [NOT FOR REPLICATION]

As your table is in merge...

try replacing this code in your from clause to where claues

FROM         dbo.PersonnelTeams

LEFT OUTER JOIN    dbo.PersonnelPositions

ON dbo.PersonnelPositions.fkPersonnelID = pkPerson1_0_

LEFT OUTER JOIN   dbo.Personnels p  

ON dbo.PersonnelTeams.fkPersonnelID = pkPerson1_0_

How you managed to detach your tempdb? As sql server doesn’t allow to detach any of the system db's.

Will my sql server work with out any issue after coping the data back to new drive ?

Column name with space is not possible as it will be recognized as next argument.

I didn't got your second question.

Is you app is OLTP or OLAP ?

How you are access the data from app is it the SP/view or simple t-sql ?

Check if the user from which you are connecting to db has the valid access to the db.

Ensure that MSDB & MASTER DB is not used by any other service or their is no active instance from EM or QA from other client machine.

If you are installing new instance its better to install with sp4 as there won't be any other patches from MS as sql 2005 is already in market.

sp4 is more then 1...

Can you give some more information about the user & his exesting access to db?

Give the command as well which you are executing to deny access to the user.

Thank you for your suggestions.

I will let you guys know what steps we exactly followed for HDD up gradation.