I need to sync SQL server database with the Interbase DB. Interbase is the live DB and main application works on this. Now customer wants to cerate an SQL server database and sync it with the live interbase database once everyday. All historical reports will be generated from the SQL Server database.
The Interbase DB does not have timestamp or any column that contains time. Hence I cound not found any way to identify new (and modified also) records. Any idea?
You can take a look at CopyTiger
Related
In my SQL Server database I need to mantain the tables linked and in sync with the tables of an MS Access .mdb file.
Lets say I update something or add something in the MS Access database via my own application.
I want those changes reflected in the SQL Server database.
I need a way to push the updates to the SQL Server database, or a way to update the SQL Server database with the new data when I connecto to it.
Trying to be clear: source must be the .mdb file database and destination must be the SQL server database. I need to keep them in sync.
Both databases have the same tables.
I have read a lot of posts, even this one: From SQL Server how do I read from an MS Access database to UPDATE data in one or more table columns? that seems to be the solution, but I can figure out the steps.
The official tool for this is:
SQL Server Migration Assistant for Access (AccessToSQL)
It has a migration feature that, when run, will replicate (adjust) the table schema in the database in SQL Server to match that of the Access database.
I want to transfer SQL Server data to Oracle tables on a daily basis.
What's the best way to do it? I am using Windows 7 as OS and SQL Developer as a tool.
Please suggest.
Thanks.
You can setup a transactional replication and create a non-sql server subscriber in oracle.
See : https://learn.microsoft.com/en-us/sql/relational-databases/replication/non-sql/non-sql-server-subscribers
Or if you only need the data to be updated once a day, consider to use snapshot replication.
Both transaction and snapshot replication can have a non-sql server subscriber.
You can use the built in Export Data command to generate an SSIS package that you can then run on a daily basis.
1) Right click on the data base in SSMS on the Object Explorer Window.
2) Select 'Tasks' from the pop-up window.
3) Click on Export Data.
4) Choose a data source (SQL Server Data Base)
5) Choose data destination as Oracle
At the end of the GUI you can save it as a SSIS package. Please do so and you can then run it either as a SQL Server Agent job or at the Windows level by using the DTEXEC command. My biggest challange when doing this is getting credentials on Oracle that allows writing and finding the correct ORA file.
I have a request to dump periodically, every 15 minutes, data from a SQL Server database and move it to an Oracle database.
This activity will go under a scheduler like Tivoli.
Have Oracle or SQL Server some way to do this? Or, is there some product or workaround to satisfy this request?
Thanks a lot in advance
SQL Server Integration Services sounds like a good starting point
You can set up replication from SQL Server with an Oracle subscriber. This will keep the Oracle table up to date in real-time, changes applied to the SQL Server table are immediately applied to the Oracle table as well.
I have an Oracle 10G database running on a Unix environmnent and have a requirement to write a PL/SQL job that will be running on the Oracle database that will populate tables in another database which is a microsoft SQL Server database running on a Windows platform.
Having looked around, it looks like this is possible via database links. Has anyone got any more information on this? For example how reliable is the connection and are there any disadvantages in having such a setup?
Chances are that i would have limited access to the SQL Server database. Is the above possible without having to make any changes to the SQL server database? (Assuming the DBA on the SQL server has configured the database to be accessed from other databases)
Thanks
Use the Oracle feature DG4ODBC, it is as reliable as any normal DBLINK setup, to the SQL Server side it will look like any other sort of client connection. You only need to do anything more elaborate if you are planning to do distributed transactions between Oracle and SQL Server (i.e. 2 Phase Commit). You will probably also want UnixODBC and FreeTDS.
We are planning on using the new auditing feature in SQL Server 2008. Is there a way to configure the auditing component to insert audit data to a separate database?
I don't believe so. It's to-file (rolling log) or to event viewer. This is a good reference: http://www.sqldbatips.com/showarticle.asp?ID=133