I have encouraged our DBA team to get powershell installed (SQL 2005) - no luck yet. Meanwhile I use a procedure for each partitioning function. Here is an...

Not directly related to article - but - an alternative to spt_values:

create table #Number (number int);

with N4000 as (select 0 as Number union all select Number+1 from N4000 where Number...

Back to the idea that it is a firewall issue - I tried adding this before the open and still no luck (still getting null back).

EXEC @Result = sp_OAMethod...

We think it might be some firewall rule - but here are some commands I tried:

EXEC spGeocode @Address = '1234 N. Main Street', @City = 'Santa Ana', @State = 'CA'

or

EXEC...

I implemented the code (including reconfigure for OLE auto and show advanced) and the procedure returns nulls - I used example address from article. I took the URL from...

One of the beauties of proxy and abstracting permissions for a job step is to not tie the step's requirements to the account running the job or the service the...

We use proxy account / credentials and assign this account to the Run As property on a job step. The job does not have to be run under the...

The extension hardening got a little harder trying to name file with xlsx extension.

When I change C# source to have xlsx extension the Excel file will not open. Granted...

I found this link helpful - but a better solution would be that the document generated be in Office 2007 format.

http://www.itexperience.net/2008/03/17/excel-2007-error-different-format-than-specified-by-the-file-extension/

I tested it successfully with SQL 2005. Two questions / statements - When I double click on the xls file I get a message that the file you are...

Thank you for the article.

I implemented it with idea that I would include the source row's key field in the xml column - in this way one could look...

I wish there were more responses from data warehouse applications. When I first started in DW environemt it was a mantra (supported/promoted by our architect and MS consultant) no...

If the end goal isn't immediate row by row processing - don't forget about the SQL 2005 OUTPUT clause that can be used with INSERT, UPDATE and DELETE. 

There should be caveats for these types of assertions.  In a data warehouse you would experience significant performance penalties always using declarative referential integrity.  In DW world it is the...