contact your network team and tell them to open the port on this server.

try to do the telnet with sqlip sqlportnumber.

Is it responding from both machine?

not sure what kind of job is that and how many steps in it but as all the job and steps will be in msdb database, you can create one...

When i logged in NODE1 & open SSMS connecting through HEARTBEAT instance name, connecting fine but when i tried to connect through IP not able to connecting and i tried...

two option

1) Make your database offline, and whoever shouts of "connection error" is the source.

2) In profile, put the object id/name which is related to your database and is being...

try to connect with ip and portnumber.

Also check on the actual SQL server,

either TCP/IP and any other required protocol is enabled for sql server or not.

declare a global variable and update the value in that variable at start of the package. Use the same variable in all steps.

There is limited space so restoring the database to the new R2 instance is out of the question. Do you know issues or concerns with detaching and reattach the db...

why not?

The quickest way will be re-configure the replication for the specified database.

if your datafiles are equal in space then data will be spread almost equally. The different will not be mush to cry out for.

Thanks for the lovely script.

I customised it with rebuild for more than 30% and reorg for more than 50% and only for those where page count is > 50. All...

there is a report that you can run that till tell you who last changed the stored procedure and when. from ssms navigate to your database, right mouse click on...

its because, sql not able to understand

alter database @databasename set recovery simple

in your code.

If you put this in some variable, like I did in @sql and then exec...

I think the error is here

Error string: OLE DB provider 'MSDASQL' reported an error. Error source: Microsoft OLE...