The code below is nothing fancy but you can schedule something simple as below. You can replace $INST1 with your Service name and you can replace echo "hello" with some command...

You can use the dtsrun utility directly from the command prompt

You don't have to create an ODBC. Just give you servername in Data Source

Try re-building your indexes if CHECKTABLE or CHECKALLOC doesn't help.

Right click Linked Servers and click on New Linked Servers.

Enter say test(or anything else) as the name of the linked server.

Under server type, select the option other data source...

SQL server will use shared lock for the above.  Can you please describe what you are trying to achieve.The article below has some more information.

http://databasejournal.com/features/mssql/article.php/3289661

You can specify an alias for a linked server.  Select the datasource to be other data source and select the driver for SQL server.

Not only the entries above but you might want to search for all the entries for the virtual name and delete them all.

Run the SQL installer and select advanced options. Select the option of Maintain a virtual Server for Failover clustering. You can check this article also.

http://www.databasejournal.com/features/mssql/article.php/10894_3467291_1

That's good. Just curious. Why do you need to shut down sql to perform maintenance on your system ?

select filegroup_name(groupid) as filegroup ,object_name(id) as table_name from sysindexes where indid = 255

Check for any references to the old instance in the registry and try deleting them.

tempdb gets re-created everytime SQL server starts up.

You can change the location of tempdb by specifying alter database tempdb modify file name='tempdb',filename = '' and then re-start sql services

or

Stop...

can you try to execute sqlservr.exe directly from the command prompt and see if sql services starts or not ? The .exe canbe found under \microsoft SQL Server\MSSQL\Binn\

Do a dbcc updateusage and that will update the count in enterprise manager.