|
Home > Archive > MS SQL Server OLAP > March 2006 > OLEDB Provider for ODBC
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
OLEDB Provider for ODBC
|
|
|
| Posted this before but I lost access for a few days and it has been lost in
the past -
Very simple problem. In SQL Server 2000, when I create a new data source for
an Analysis Services cube, one of the providers available is 'OLE DB Provider
for ODBC Drivers'. In SQL Server 2005 when I try to do the same thing, I no
longer have the ODBC provider available. I believe this is part of MDAC which
is loaded as part of the operating system (I believe that I have the actual
dll on the machine) - I am using Windows XP Professional.
I need to access an ODBC compliant data source from MSAS 2005 that does not
have a native OLE DB compliant driver available. Anyone help? For
information, the database to be accessed is a VLDB environment Whitecross.
| |
| Dave Wickert [MSFT] 2006-03-24, 11:39 am |
| The OLEDB Provider for ODBC that shipped with SQL2K was dropped in SQL2K5.
Your best option for getting ODBC data into Analysis Services is to use SSIS
to read the data into a pipeline and then load the data into Analysis
Services from there. In SSIS, use the managed .NET adapter for ODBC. You
still need a supported RDBMS to design and build the Analysis Services
objects, either SQL Server 2000 or 2005, Oracle, DB2, or Jet (using the
managed .NET adapter). I know that seems like a lot of work, but
unfortunately that is the only way to do it in Analsyis Services 2K5.
--
Dave Wickert [MSFT]
dwickert@online.microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"JC" <JC@discussions.microsoft.com> wrote in message
news:CF421109-27DC-49ED-9DD4- 12A74F64F3DC@microso
ft.com...
> Posted this before but I lost access for a few days and it has been lost
> in
> the past -
>
> Very simple problem. In SQL Server 2000, when I create a new data source
> for
> an Analysis Services cube, one of the providers available is 'OLE DB
> Provider
> for ODBC Drivers'. In SQL Server 2005 when I try to do the same thing, I
> no
> longer have the ODBC provider available. I believe this is part of MDAC
> which
> is loaded as part of the operating system (I believe that I have the
> actual
> dll on the machine) - I am using Windows XP Professional.
>
> I need to access an ODBC compliant data source from MSAS 2005 that does
> not
> have a native OLE DB compliant driver available. Anyone help? For
> information, the database to be accessed is a VLDB environment Whitecross.
>
| |
|
| Oh dear! This is a VLDB environment with, potentially, tens of terabytes of
data! Not something I want to pull in at all.
Thanks for you help all the same.
"Dave Wickert [MSFT]" wrote:
> The OLEDB Provider for ODBC that shipped with SQL2K was dropped in SQL2K5.
> Your best option for getting ODBC data into Analysis Services is to use SSIS
> to read the data into a pipeline and then load the data into Analysis
> Services from there. In SSIS, use the managed .NET adapter for ODBC. You
> still need a supported RDBMS to design and build the Analysis Services
> objects, either SQL Server 2000 or 2005, Oracle, DB2, or Jet (using the
> managed .NET adapter). I know that seems like a lot of work, but
> unfortunately that is the only way to do it in Analsyis Services 2K5.
> --
> Dave Wickert [MSFT]
> dwickert@online.microsoft.com
> Program Manager
> BI Systems Team
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "JC" <JC@discussions.microsoft.com> wrote in message
> news:CF421109-27DC-49ED-9DD4- 12A74F64F3DC@microso
ft.com...
>
>
>
| |
| Darren Gosbell 2006-03-28, 7:29 am |
| SSIS has a "push" processing task that you can use to read data directly
from the source system and push directly into the MOLAP store. You do
not need to store a staged copy of the data as you would have had to
with AS2k.
--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell
In article <A10D8AD3-FE99-404A-B5B8- 9D499ED15110@microso
ft.com>,
JC@discussions.microsoft.com says...[color=darkred]
> Oh dear! This is a VLDB environment with, potentially, tens of terabytes of
> data! Not something I want to pull in at all.
>
> Thanks for you help all the same.
>
> "Dave Wickert [MSFT]" wrote:
>
|
|
|
|
|