Deferred Processing - All Comments

re: PowerShell and ADO.NET

Nick — Fri, 01 Aug 2008 18:10:31 GMT

Hey,

Thanks for this blog entry, I figured out how to add a column to an existing dataset table. Now how would I populate the values in the column / rows (I need to combine a 1st name field and a last name field into a "full_name" field).

re: Evaluating String Arithmetic Expressions in SQL Server 2005

Need Help — Thu, 22 May 2008 20:35:00 GMT

Where should I be putting the c# code? in SQL Server or in VS 2005

re: PowerShell and ADO.NET

bk — Tue, 18 Mar 2008 21:07:00 GMT

Awesome tutorial!!

re: Processing XML with PowerShell II

Edward Benson — Tue, 18 Mar 2008 11:16:00 GMT

Very helpful article, thank you!

The %{$_.Property} notation had me completely foxed, until I found out that % is alias of "ForEach-Object" (Using command "Get-Alias %").

Using "ForEach-Object", in place of "%", would make the code much clearer. And "Select-Object" would be clearer still.

re: PowerSMO!

Dan — Tue, 26 Feb 2008 10:51:00 GMT

You can save it using IE to make an MHT archive that you can pass around. In IE-7 use Page->Save As->Web Archive Single File. You can view the *.mht file that it produces without being on line.

Dan

re: PowerSMO!

Tracy Esau — Tue, 26 Feb 2008 03:16:00 GMT

can u please upload a pdf version so that we can read the article under our convinence

re: PowerShell and XmlDocument

ScriptRunner — Tue, 18 Dec 2007 18:13:00 GMT

Nice article, very helpful...

re: Evaluating String Arithmetic Expressions in SQL Server 2005

Maddy — Wed, 17 Oct 2007 12:10:00 GMT

I tried deploying the CLR function given above. Now when i try to execute the function from SQL server, It's not giving the proper results.
Like if I pass the parameter as 1+2+3, then it return me value of 1 i.e. always returns the 1st number.

re: Evaluating String Arithmetic Expressions in SQL Server 2005

Senthil — Wed, 29 Aug 2007 03:24:00 GMT

Hi,
When i try to create the procedure it throws this error
Msg 6567, Level 16, State 2, Procedure EvaluateArithmethicExpression, Line 1
CREATE PROCEDURE failed because a CLR Procedure may only be defined on CLR methods that return either SqlInt32, System.Int32, void.

this is my Procedure
CREATE PROCEDURE EvaluateArithmethicExpression
@input nvarchar(200)
AS EXTERNAL NAME
ArithmeticCalculations.ArithmeticCalculations.EvaluateArithmethicExpression

re: PowerShell and ADO.NET

Dmitri Zimin(e) — Tue, 31 Jul 2007 20:46:00 GMT

Dan
thank you for a good walk-through, it is great to show the powererful way of using .NET directly, and very practical - I was looking for exactly this - the way to use ADO.NET rather then ADO for hooking into DB.

Bug report:
$connString = "server=.;integrated security;database=northwind"
but should be:
$connString = "server=.;integrated security=true;database=northwind"

re: Comparing XML in SQL Server 2005

Jayaram Krishnaswamy — Sat, 21 Jul 2007 18:44:00 GMT

You can use an XML task in SSIS to do the comparison

re: PowerSMO!

ppsqualo@gmail.com — Thu, 12 Jul 2007 10:04:00 GMT

Thanks Dan,
I used powersmo to download all AD users.
Who is interested can copy the script from my blog http://ppsqualo.blogspot.com/2007/07/scaricare-tutta-la-foresta-ad-in.html
Thanks ..

re: PowerShell and ADO.NET

Cash Foley — Sat, 30 Jun 2007 14:17:00 GMT

Gregory (from previous comment). This is not COM objects. This is using .NET ADO.NET

As to the broad objection that MS is not "trying to move scripters away from [COM]", they are making it more unnecessary to use COM. Powershell enables access to many "Object" technologies on the platform including COM and WMI. Access to .Net classes opens huge alternatives.

I'm glad MS didn't take an approach of steering me away from COM by not supporting it in Powershell. Powershell is all about "getting things done" and its seamless bridging of these technologies is amazing. If you don't like COM, you dont' have to use it.

re: CLR Based Histogram Functions and SQL Server 2005

Seth Schroeder — Tue, 12 Jun 2007 22:59:00 GMT

Here's an alternate approach for an equiwidth histogram. It also features an (almost) arbitrary number of buckets:

http://www.nearinfinity.com/blogs/page/seths?entry=quick_and_dirty_sql_histogram

re: PowerShell and ADO.NET

Gregory Barton — Tue, 29 May 2007 19:41:00 GMT

Thanks for this info. Although Powershell is built on .NET, it seems all of Microsoft's examples tend to still use COM objects. I figured they would try to move scripters away from that, but the evidence is not there.