PostParentID is one

Yes change the account of sql server agent via SQL configuration manger and make it same as SQL Server

http://msdn.microsoft.com/en-us/library/ms188783.aspx

Refer Example G. Creating an index with included (non-key) columns

What Class are you using to connecto to SQL Server? If you are using a standard SqlConnection and SqlCommands, then it should work just fine. These are both...

Check their may be other jobs associated with this job. try deleting maintenance plan instead of its job

Check windows event viewer you will be getting some error message their.

Send that error message to us.

Man @full_backup_path is empty, please fill it.

Hi

you can add different steps to your job, like in step 1 backup in step 2 restore and then in step 3 post restore thing. And in step properties...

To increase performance of this as suggested create index on ParentPostID and add all columns in select as included.

Try this:

DECLARE

@data_file_path VARCHAR(512)

, @log_file_path VARCHAR(512)

, @backup_path VARCHAR(512)

, @backup_extension VARCHAR(4)

, @mdf_extension VARCHAR(4)

, @ldf_extension VARCHAR(4)

, @cnv_extension VARCHAR(4)

, @backup_name NVARCHAR(8)

, @database_name VARCHAR(32)

, @restore_name VARCHAR(32)

, @logical_data_name VARCHAR(64)

, @logical_data_1_name VARCHAR(64)

, @logical_log_name VARCHAR(64)

, @data_file_full_path NVARCHAR(255)

,...

Their is as such no straight forward solution for this, but you can do one thing create DDL trigger check for schema change of function, if user is changing schema...

Try this

Declare @data_file_full_path nvarchar(255),@log_file_full_path nvarchar(255)

and when assigning values to @log_file_full_path and @data_file_full_path convert them to nvarchar

RESTORE DATABASE @restore_name FROM DISK = @full_backup_path WITH FILE = 1,

MOVE N'U4SConvert_Data' TO...

May be your tempdb need more then fre space so please follow the steps which I have given and also add datafile size to 2MB in alter db command.

As per you steps it seems like you have to change the password of SQL Server which are associated to Cluster, if correct then these steps are fine and yes...

This error is related to tempdb, SQL Server is not able to allocate space to tempdb.

Do you know where your tempdb resides, if yes check the drive and free up...