A SQL login already has permissions to ALTER LOGIN and can use that to change their password.  I would not recommend allowing them to set the password to never -...

I would also recommend using synonyms - and possibly a separate schema for the synonyms.  This would allow you to change the linked server and update just the synonyms without...

In the  article you mention PoSH as well, and my tool of choice (despite the bugs I've found and live with) is Powershell Plus Professional Edition (which is free). ...

You will need a third-node in your cluster - licensed with Enterprise Edition.  I would not put SSRS on this server - but it can be...

This third-node does not have...

This seems to be a typical gaps & islands issue...here is another method:

Declare @test1 Table (id int, startdate datetime, enddate datetime);

 Insert Into @test1 (id, startdate, enddate)
...

Are there any entries in the mapping section above this?  It seems the issue is related to the user accessing the linked server - is it possible that the sa...

You can rewrite the script to run in SQLCMD mode:

:connect YourServerName
:out \\somesharename\somefilename.txt

    Set Nocount On;

 Select ...
   From first_table
  Where somecriteria;

...

How is the linked server security defined?  Is it a fixed username/password or do you have some type of mapping set up?

It depends...

Why are you joining the 2 tables and what data does each table contain?  For example, if table1 contains sales data - and has a column named StateID, and...

The rounding still takes place in the wrong spot.  Sergiy actually posted what is wrong that in his article this morning although he didn't include the bit of performance...

The reason the columns do not line up is because you have commas in the data.  To avoid this issue you need to set the text qualifier to a double-quote.

For...

I would have to see an example of the un-proper format you are getting - it seems to me that would be due to the data including CR or LF...

That is entirely possible - I don't export files to Excel.  I always export to a CSV file and let the users open it in Excel - they can then...

Try to output to a flat file - comma-separate values and see if that works better.

How are you exporting the data - what were the options you selected in the export wizard?  It should not preface a field with a single-quote like that...

It looks like...