but in that case there will be new empid for him/her. and then everything from fresh. Thats what I am assuming. Is that not the case?

you might already checked the history tab in replication monitor, are you not getting anythere there? Is it quiet long period since when your data is out of sync?

if you have any tool for performance analysis then you can browse history to see what type of lock was there and other related problems. Else might find something in...

there is a utility tablediff which you can google.

It compare the mentioned tables and generate the difference between tables. Very helpfull in replication.

is there any fix period for the gap for any employee..

like an employee can have max 22 days of leave in year or something like with other holidays/leave.

you can put...

as you doing on t-sql, the same you can do by SSMS.

expand your table, expand indexes and then right click on the index which you want to disable and then...

then i think its already answered here..

http://www.sqlservercentral.com/Forums/Topic969573-338-1.aspx.

you should first search the site for your problem and if not able to see answer then only post your question...

what do you mean by generating an index?? whcih index and how they are getting aut generated? did you mean auto updated?

if table not already created then

select ccode, substring(vcode,1,1) into mytable from youroriginaltable

if you already created your destination table(mytable) then do insert into instead of select .. into..

hope it helps

Sorry to hear, just suggestion, can you try to run repair for sql server?

why not suggest to run sp_help tablename and then you will get all details for that table including individual column name. then you can select required columns and copy paste...

how to find out who disabled sql agent jobs?

what do you mean by sqlagent jobs?

Is it about any perticular job or complete sql agent?

Whatever the case check error logs...

"you must resolve any issues with the previous operation that failed"

that is the only assumption I have from this error.

it seems like there was some installation in past which required server reboot and was not done.

I think reboot will resolve this problem.

lot of articles available on BOL for upgrade.