Is it faster to use 1 type of provider over the other? We are using SSIS (SQL Server 2005) to pull some data from Oracle and import it into SQL Server. It was my understanding that OLEDB is faster, because the connection is native, and the data isn't being run through any .NET code?
Is this correct?
OLEBD will work faster for sure.
But you will have to make a choice between Microsoft or Oracle driver for the oracle database. I recommend you to try both and decide which one offers you a better performance.
I've heard that oracle's drivers have improved quite a lot on ssis 2008 (writing performance was horrible).
That depends! From .NET code you would always prefer using the Oracle .NET provider to access a Oracle database. Recon you would want to use the .NET provider from SSIS as wel
Related
Don't know if anyone can help but i have been tasked with getting all the information out of an Ingres DB into a SQL Server DB. I have virtually no experience of Ingres apart from fumbling my way through looking at what it does and how it does it.
Ideally, what i would like to do is create a linked server (if possible) on a SQL Server and query the data that way. has anyone done this in the past previously and if so, any guidance/help would be appreciated
Thanks
You're got two choices ODBC or the Ingres .NET Data Provider. I suspect the Ingres .NET Data Provider is more capable, but you may find ODBC meets your requirements.
The Ingres .NET Data Provider requires the Data Access Server process (iigcd) to be running in your Ingres installation.
https://docs.actian.com/ingres/11.0/index.html#page/Connectivity%2FConnectivity_Title.htm%23
What version of Ingres are you running?
I have to import about 50000 rows from a view in sql server into postgresql.
Sql server is 2000 version
Postgresql is 8.X
I thought it was an easy task and I could accomplish it exporting into a csv file.
I'm having lots of trouble and I lost too much time on this task, so I'm looking for an alternative. Is there a well tested way to import data from sql server ? I searched on internet and found some magic migration software but I have a quite simple goal (a single table to import) and I would like to avoid installing untrusted and unknown software.
Two more possibilities come to my mind: use enterprise manager to connect to Postegresql (with OBCD driver ?) or pgadmin to connect to sql server. Are they both feasible ?
Thanks
Filippo
One my clients has a system written in Delphi 3 and the database is Paradox. My job is to convert it to use SQL Server 2008. How can I make it connect to SQL 2008?
This is pretty old stuff, I know. I appreciate the help.
Thanks
At the very least BDE should be able connect using ODBC and choosing the SQL 2008 Driver in ODBC. I haven't tried, but I doubt that the BDE SQL driver will connect to SQL 2008, and I doubt anybody will develop a BDE driver for 2k8.
Do you intend on moving from Delphi 3? If so, then SDAC (SQL Server Direct Access Components) from Devart would be worth looking at. They support SQL Server 2008 but unfortunately require Delphi 5 or above. They use OLE DB and any Windows machine with 2000 or above will have the drivers installed (which is part of Microsoft Data Access Components - MDAC).
You can use ADO without using Ado Components, by importing ActiveX Data Objects Library, but this will require more work.
Why not upgrade the project to Delphi 2007 as a stepping stone towards the future? There have been many improvements and bug fixes to the language since Delphi 3 that you could easily take care of. The pain of migration might be much easier than dealing with issues which have been already addressed and corrected in the latest versions of the compiler.
You can try one of the Free Components from Torry.net to connect to the SQL server using ADO.
Check TaoADODataSet and Free ADO Dataset in the page http://www.torry.net/pages.php?id=569. These components have Delphi 3 support.
Could someone suggest a shared SQL Server solution that supports DTS packages?
Update:
I was hoping to use the PostgreSQL ODBC driver and a DTS package to keep data synchronized between MSSQL server and Postgres. After getting my hands on SQL Server 2005 and attempting to do this I realized SSIS doesn't seem to play nicely with the PostgreSQL ODBC driver.
I gave up on the SSIS/DTS solution and have written a program using JDBC which runs happily on my Linux server.
I am not aware of any hosting services that provide DTS or SSIS as a feature. However, if what you are trying to achieve by using DTS/SSIS is a way to do your own backups/data transfers then I would suggest you look into the Microsoft SQL Server Database Publishing Services. Go Daddy supports it.
I have used Edgewebhosting before and used DTS packages for pushing data to sites. I have no affiliation with them, it worked well for the job.
I usually use Delphi-targeted databases for most of my work (NexusDB typically, lately), but still have bad memories of how painfully slow connecting (and posting) to MS Access was via ADO. I have a new project that may need to target MS SQL Server. For D2007 Pro, what is the best way to connect to MS SQL Server? (Third party components = fine, if that's the best route).
The TADOConnection really isn't that bad. Access was never intended to be a production RDBMS. ADO works much faster with SQL Server than with Access. See http://support.microsoft.com/kb/225048 for some of the reasons why.
The AnyDAC offers great feature set and performance, as simplifies development of the database applications. AnyDAC supports MS SQL Server, MS Access and much more.
The UniDac Component from DevArt / Corelab is your best option
It offers fast performance and you can talk to a number of differrent databases
I always recommended DevArt db components fro their performance and reliability.
You can choose between SDAC(for direct access to sql server) or UniDac (direct access to Sql server, Oracle, MySql,PostgreSql and Interbase/firebird)
if you don't require the advanced components that access specific features of sql server like TMSChangeNotification, TMSTransaction or TMSServiceBroker, then you can go with UniDac so your application will be designed to work with multiple databases.
Devart offer components and dbExpress drivers for accessing SQL Server databases. The also have UniDAC which supports other databases as well.
Da-soft AnyDac supports SQL Server and other databases.
Bob Swart has published Delphi for Win32 VCL Database Development on Lulu, if you need any help.
I use ADO to connect to Sql Server since Delphi 7 and it always worked great