Best Practices/Provider connecting to an Oracle Database?

Are there generalized best practices with regards to which method/provider to use when accessing an Oracle database? I have used both the "Native OLE DB\Microsoft OLE DB Provider for Oracle" and the "Native OLE DB\Oracle Provider for OLE DB" and both seem to have their own quirks (requirement to convert to Unicode, etc) but I also have heard that I shouldn't be using an "OLE DB" source at all, but to set it up as an ADO .Net connection.

We are just beginning to implement SSIS, and are trying to establish Best Practices/Standards etc.

Are there any gotchas - performance and/or otherwise I should know about?

Thanks in advance!

I'm assuming you've looked at the SSIS Connectivity whitepaper at http://ssis.wik.is/File:Connectivity_White_Paper/Connectivity_and_SQL_Server_Integration_Services_forum_post.doc (Oracle connectivity section).

We have plans to benchmark connectors in the future, when we might be able to share best practices and performance stats.

Best Practices Analyzer for Sql Server 2005

Hi, Is there a version for this tool available for 2005? or do you know if new release is comming soon ?

Regards.

There is no version available yet. I haven't heard of any coming releases yet.|||

I'm a program manager at Microsoft in SQL Server. We've decided to make a new Best Practices Analyzer tool which will support SQL Server 2005. For more information or to provide some feedback go to: http://blogs.msdn.com/sqlrem/archive/2006/04/06/570292.aspx.

Thanks,

Paul A. Mestemaker II
Program Manager
Microsoft Corporation
SQL Server Relational Engine Manageability Team

Best Practices Analyzer for Sql Server 2005

Hi, Is there a version for this tool available for 2005? or do you know if new release is comming soon ?

Regards.

There is no version available yet. I haven't heard of any coming releases yet.|||

I'm a program manager at Microsoft in SQL Server. We've decided to make a new Best Practices Analyzer tool which will support SQL Server 2005. For more information or to provide some feedback go to: http://blogs.msdn.com/sqlrem/archive/2006/04/06/570292.aspx.

Thanks,

Paul A. Mestemaker II
Program Manager
Microsoft Corporation
SQL Server Relational Engine Manageability Team

best practice for disk paritioning

Can anyone please tell me what the best practice is for SQL 2000 on a
WIndows 2003 server with regards to disk paritioning? My standard setup is
c:/d: on mirrored disk array (c is for OS, d for data) and all other data on
a SAN. What is the best way to configure sql?
What other data is there except data<g>. A logical partition does nothing
for performance if it is on the same drive array as something you are trying
to keep it away from. While C: is great for the OS and SQL Binaries you are
best to place the data and logs on the SAN.
Andrew J. Kelly SQL MVP
"Bad Beagle" <maxwelli@.shaw.ca> wrote in message
news:%23IbisWnzEHA.260@.TK2MSFTNGP11.phx.gbl...
> Can anyone please tell me what the best practice is for SQL 2000 on a
> WIndows 2003 server with regards to disk paritioning? My standard setup
> is c:/d: on mirrored disk array (c is for OS, d for data) and all other
> data on a SAN. What is the best way to configure sql?
>

best practice for disk paritioning

Can anyone please tell me what the best practice is for SQL 2000 on a
WIndows 2003 server with regards to disk paritioning? My standard setup is
c:/d: on mirrored disk array (c is for OS, d for data) and all other data on
a SAN. What is the best way to configure sql?What other data is there except data<g>. A logical partition does nothing
for performance if it is on the same drive array as something you are trying
to keep it away from. While C: is great for the OS and SQL Binaries you are
best to place the data and logs on the SAN.
--
Andrew J. Kelly SQL MVP
"Bad Beagle" <maxwelli@.shaw.ca> wrote in message
news:%23IbisWnzEHA.260@.TK2MSFTNGP11.phx.gbl...
> Can anyone please tell me what the best practice is for SQL 2000 on a
> WIndows 2003 server with regards to disk paritioning? My standard setup
> is c:/d: on mirrored disk array (c is for OS, d for data) and all other
> data on a SAN. What is the best way to configure sql?
>

best practice for disk paritioning

Can anyone please tell me what the best practice is for SQL 2000 on a
WIndows 2003 server with regards to disk paritioning? My standard setup is
c:/d: on mirrored disk array (c is for OS, d for data) and all other data on
a SAN. What is the best way to configure sql?What other data is there except data<g>. A logical partition does nothing
for performance if it is on the same drive array as something you are trying
to keep it away from. While C: is great for the OS and SQL Binaries you are
best to place the data and logs on the SAN.
Andrew J. Kelly SQL MVP
"Bad Beagle" <maxwelli@.shaw.ca> wrote in message
news:%23IbisWnzEHA.260@.TK2MSFTNGP11.phx.gbl...
> Can anyone please tell me what the best practice is for SQL 2000 on a
> WIndows 2003 server with regards to disk paritioning? My standard setup
> is c:/d: on mirrored disk array (c is for OS, d for data) and all other
> data on a SAN. What is the best way to configure sql?
>