Getting Started with the CData PowerShell Cmdlets for Sybase Data
This guide explains everything you need to get started with the Sybase PowerShell Cmdlets. You'll learn how to install the cmdlets, configure your first connection, run queries, and explore next steps for working with Sybase data in PowerShell.
Installation & Licensing
System Requirements
CData PowerShell Cmdlets run anywhere PowerShell runs.
Windows
- Windows 10/11
- Windows Server 2016+
- PowerShell 5.1 or PowerShell 7+
macOS & Linux
- PowerShell 7+
- No additional system libraries required
- No architecture-specific installers
Installing the Cmdlets
CData Cmdlets are delivered through the PowerShell Gallery, ensuring a simple and consistent installation process across platforms.
Installation Steps
- Open PowerShell in Administrator mode
- Run the following command to install the cmdlet module:
Install-Module SybaseCmdlets -Repository PSGallery -Force
This command:
- Downloads the module from the official PowerShell Gallery
- Installs it into your PowerShell environment
- Registers all cmdlets for immediate use
Module Verification
To verify installation:
Get-Module -ListAvailable "*Sybase*"
Licensing
The cmdlets support both trial and fully licensed activation.
Trial Licensing
Trial activation is automatic - no key is required. Once installed, you can begin using the cmdlets immediately.
Activating a Full License
If you have purchased a full license, you will receive a product key from the CData Orders Team.
Activate Your License
Run the following command:
Set-ModuleLicense ""
You should see a confirmation message indicating successful activation.
Common Licensing Questions
Can I use my license on multiple machines?
Depending on your subscription tier. Refer to your order confirmation or contact [email protected].
I lost my license key. What do I do?
Email [email protected] with your order number to have it resent.
Can I transfer my license to another machine?
Submit a license transfer request here: https://www.cdata.com/lic/transfer/.
Where can I manage my license?
Visit the CData Customer Portal: https://portal.cdata.com/.
Connection Configuration
Once the module is installed and licensed, you can establish a connection to Sybase using the
Connect-Sybase cmdlet
After obtaining the needed connection properties, accessing Sybase data in PowerShell and preparing for replication consists of four basic steps.
To connect to Sybase, specify the following connection properties:
- Server: Set this to the name or network address of the Sybase database instance.
- Database: Set this to the name of the Sybase database running on the specified Server.
Optionally, you can also secure your connections with TLS/SSL by setting UseSSL to true.
Sybase supports several methods for authentication including Password and Kerberos.
Connect Using Password Authentication
Set the AuthScheme to Password and set the following connection properties to use Sybase authentication.
- User: Set this to the username of the authenticating Sybase user.
- Password: Set this to the username of the authenticating Sybase user.
Connect using LDAP Authentication
To connect with LDAP authentication, configure Sybase server-side to use the LDAP authentication mechanism.
After configuring Sybase for LDAP, you can connect using the same credentials as Password authentication.
Connect Using Kerberos Authentication
To leverage Kerberos authentication, begin by enabling it setting AuthScheme to Kerberos. See the Using Kerberos section in the Help documentation for more information on using Kerberos authentication.
You can find an example connection string below:
Server=MyServer;Port=MyPort;User=SampleUser;Password=SamplePassword;Database=MyDB;Kerberos=true;KerberosKDC=MyKDC;KerberosRealm=MYREALM.COM;KerberosSPN=server-name
Collecting Sybase Data
-
Install the module:
Install-Module SybaseCmdlets
-
Connect to Sybase:
$sybase = Connect-Sybase -User $User -Password $Password -Server $Server -Database $Database -Charset $Charset
Querying Sybase Data in PowerShell
Once connected, you can query data using standard SQL like commands.
Example Query:
$results = Select-Sybase `
-Connection $conn `
-Table "Products" `
-Columns "Id,ProductName" `
-Where "Id != ''"
Display the results:
$results
You have now successfully accessed Sybase data from PowerShell!
Common Issues
Authentication Failed
Solution: Verify username, password, and security token. For OAuth applications, you may need to authorize CData in your application's security settings. Contact [email protected] for authorization assistance.
Network or Proxy Issues
Solution: Confirm firewall settings and outbound access. Most cloud applications use port 443.
Cmdlet Not Found
Solution: Ensure the module is installed-
Get-Module -ListAvailable "*Sybase*"
Slow Queries
Solution:
- Add filters to reduce dataset size
- Use $Limit or $Top properties where supported
- Contact [email protected] for optimization help
For additional connection troubleshooting, contact [email protected] with your specific error message.
What's Next?
Now that you have installed, licensed, and configured the PowerShell Cmdlets, here are some scenarios you can use to explore:
| PowerShell | Article Title |
|---|---|
| Piping Cmdlets | How to pipe Sybase Data to CSV in PowerShell |
| Replication | PowerShell Scripting to Replicate Sybase Data to MySQLl |
Get Support
If you need assistance:
- Technical Support: [email protected]
- Community Forum: CData Community Site
- Help Documentation: Installed locally and available online
FAQs (PowerShell Cmdlets)
Installation & Licensing
- Do I need administrator rights to install the cmdlets?
- Windows PowerShell 5.1 (Windows): Administrator rights are recommended, especially when installing modules for all users.
- PowerShell 7+ (Windows, macOS, Linux): You can install cmdlets for the current user without admin rights using:
Install-Module SybaseCmdlets -Scope CurrentUser
- Do I need to download an installer?
Not always.
CData PowerShell Cmdlets are delivered through the PowerShell Gallery. Installation is performed via:
Install-Module SybaseCmdlets -Repository PSGallery -Force
Connecting
- How do I connect to multiple accounts for the same data source?
Create separate connection objects-each with different authentication properties:
$conn1 = Connect-Sybase -User User1 -Password Pwd1
$conn2 = Connect-Sybase -User User2 -Password Pwd2
Cmdlets do not use ODBC DSNs. All connection properties are passed directly in
Connect-Sybase
Many cmdlets support proxy properties such as:
- ProxyServer
- ProxyPort
- ProxyUser
- ProxyPassword
Refer to the data-source-specific Help documentation.
Performance & Troubleshooting
- Why are my queries slow?
- Missing filters (e.g., no WHERE clause)
- Pulling large result sets
- Latency from cloud APIs
- Not using incremental strategies
- Filtering data (-Where parameter)
- Selecting only required columns
- Reviewing API throttling limits for your data source
- How do I enable logging?
Common causes:
Try:
Contact [email protected] for query optimization assistance.
Enable module logging with:
Set-ModuleLogging -Path "C:\logs\cdata.log" -Verbosity 3Upload the log file securely when working with CData Support.
Most cloud applications (Salesforce, HubSpot, Dynamics, Google APIs, etc.) use: HTTPS (443)
If your source requires additional ports, check its specific documentation or contact [email protected].
Install PowerShell 7 in the container and install the module:
pwsh -Command "Install-Module SybaseCmdlets -Force"Then authenticate normally.
General
- Where can I find all supported SQL/command operations?
- How often are PowerShell Cmdlets updated?
- Where can I find code examples?
- Basic queries
- Insert/update/delete
- OAuth flows
- File operations
- API integration
Each cmdlet includes a Help documentation set installed locally and available online: https://www.cdata.com/powershell/.
CData releases major annual updates plus incremental updates throughout the year. Check your customer portal or contact [email protected] for version availability.
Every Cmdlet includes examples in the Help documentation, plus online examples for many services: https://www.cdata.com/powershell/. Examples include:
For questions not covered in this FAQ, [email protected].