![]() |
VOOZH | about |
The CData Cmdlets Module for AlloyDB is a standard PowerShell module offering straightforward integration with AlloyDB. Below, you will find examples of using our AlloyDB Cmdlets with native PowerShell cmdlets.
The following connection properties are usually required in order to connect to AlloyDB.
You can also optionally set the following:
Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.
No further action is required to leverage Standard Authentication to connect.
There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.
Find instructions about authentication setup on the AlloyDB Server here.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.
This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.
The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos.
$conn = Connect-AlloyDB -User "$User" -Password "$Password" -Database "$Database" -Server "$Server" -Port "$Port"
Follow the steps below to retrieve data from the Orders table and pipe the result into to a CSV file:
Select-AlloyDB -Connection $conn -Table Orders | Select -Property * -ExcludeProperty Connection,Table,Columns | Export-Csv -Path c:\myOrdersData.csv -NoTypeInformation
You will notice that we piped the results from Select-AlloyDB into a Select-Object cmdlet and excluded some properties before piping them into an Export-Csv cmdlet. We do this because the CData Cmdlets append Connection, Table, and Columns information onto each "row" in the result set, and we do not necessarily want that information in our CSV file.
The Connection, Table, and Columns are appended to the results in order to facilitate piping results from one of the CData Cmdlets directly into another one.The following line deletes any records that match the criteria:
Select-AlloyDB -Connection $conn -Table Orders -Where "ShipCountry = USA" | Remove-AlloyDB
The cmdlets make data transformation easy as well as data cleansing. The following example loads data from a CSV file into AlloyDB, checking first whether a record already exists and needs to be updated instead of inserted.
Import-Csv -Path C:\MyOrdersUpdates.csv | %{
$record = Select-AlloyDB -Connection $AlloyDB -Table Orders -Where ("Id = `'"+$_.Id+"`'")
if($record){
Update-AlloyDB -Connection $alloydb -Table Orders -Columns ("ShipName","ShipCity") -Values ($_.ShipName, $_.ShipCity) -Where ("Id = `'"+$_.Id+"`'")
}else{
Add-AlloyDB -Connection $alloydb -Table Orders -Columns ("ShipName","ShipCity") -Values ($_.ShipName, $_.ShipCity)
}
}
As always, our goal is to simplify the way you connect to data. With cmdlets users can install a data module, set the connection properties, and start building. Download Cmdlets and start working with your data in PowerShell today!
Download a free trial of the AlloyDB Cmdlets to get started:
Download NowLearn more:
👁 AlloyDB IconAn easy-to-use set of PowerShell Cmdlets offering real-time access to AlloyDB. The Cmdlets allow users to easily read, write, update, and delete live data - just like working with SQL server.