Oracle
as a Data Source, Setting
up Oracle as a Data Source for SQL Server and Configuring
Oracle as a Data Source for SQL Server address
the use of replication within SQL Server where Oracle was used as the data
source, and many of the comparisons or mappings back into Oracle are addressed
therein, so I’ll pass on repeating this material and move on to the next
category.
Replication
The next
major category in SQL Server Management Studio’s (SSMS) Object Explorer tree deals
with replication.
Management
Many of the
administration-like features of Oracle can be found under Management.
To begin with,
Maintenance Plans are quite similar to procedures you would call within a job
or schedule in Oracle, for example, a requirement to purge or archive data in
an Oracle schema. The stored procedure defines what is to be done when the
procedure runs. The archive and purge job example could be defined via a plan
in MSSQL as well, or you could easily define a plan that takes care of your
backups (although not everyone thinks a maintenance plan is the best way to go
about running backups, but Microsoft thought it was useful, so that’s why it
can be done). Many common “ash and trash” tasks are already pre-defined in
MSSQL. Right-click Maintenance Plans and start creating a new plan via the
wizard. In the bottom left corner of the design pane, you see a list of those
tasks.
Many of the
tasks are things DBAs did quite often in older versions of Oracle because there
was no automated or built-in mechanism in Oracle that would do them. The updating
of statistics is fairly well automated starting with release 10g, and
MSSQL does it too, but it can be done more often if need be (especially after
significant changes, so no need to wait for a nightly maintenance window to
open).
View article
Back to DBAsupport.com
