|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Monday, December 17, 2012 4:21 PM
Points: 74,
Visits: 316
|
|
| I have a tool that uses SSIS and stored procedures to extract data from a non-SQL Server database (Sybase) and loads the data into a SQL Server database. I have upgraded to SQL Server 2008 R2 and I am in the process of upgrading to Powershell 2.0. I want to wrap this process in a Powershell script and I would like to be able to remove SSIS from the equation if there is an OLEDB type SMO object available which would allow me to connect to a Sybase database source and manage the data in much the same way as I manage SQL Server databases through the use of SMO.
|
|
|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Wednesday, April 10, 2013 12:46 AM
Points: 90,
Visits: 124
|
|
Hello,
What does that mean SMO ? = SQL Server Management Objects SMO , when it connects to an instance , is using a ServerConnection object , itself using a SqlConnection object which cannot be used with databases which are not included in a SQL Server instance. For what you want to do ( if i have well understood ), you should rely on a linked server.
But there is some classes in the namespace System.Data.Oledb which could help you like OledbConnection, OledbCommand For that, i suggest you to have a look at this link :
http://msdn.microsoft.com/en-us/library/system.data.oledb(v=VS.90).aspx
Have a nice day
|
|
|
|