Create DataMiningStructure Continued

When I add a referrence to

Imports Microsoft.AnalysisServices.AdomdClient

Imports Microsoft.AnalysisServices.AdomdClient.AdomdConnection,\

Because I need the for an adomd connection

I receive the following problem

'MiningStructre' is ambiguous, imported from the namespaces or types
'Microsoft.AnalysisServices.AdomdClient', 'Microsoft.AnalysisServices'

with any Mining structure declaration like Dim m_ms As MiningStructure

Your project seems to contain a reference to both Microsoft.AnalysisServices.dll (AMO -- Analysis Management Objects) AND Microsoft.AnalysisServices.AdomdClient(Adomd.Net). Both these libraries contain a Mining Structure object, but they are intended for different purposes.

An AMO Mining Structure allows an administrator to tweak any properties of a mining structure in order to deploy it on a server

An Adomd.Net Mining Structure is a simpler read-only object, which allows any user with certain permissions on the server to inspect the properties of an existing mining structure.

Consider one of the following:

- use only the library that is necessary for your task, i.e. either AMO (for administrative tasks) or Adomd.Net (for querying tasks plus some modeling tasks)

- use a qualified name in defining your obejcts:

Dim m_ms as Microsoft.AnalysisServices.MiningStructure or

Dim m_ms as Microsoft.AnalysisServices.AdomdClient.MiningStructure

Create database within SSIS package

I want to create a package that imports data from a Visual Foxpro database to SQL Server 2005 Express database. I used the wizard in BI Development Studio (similar to the DTS in SQL Server 2000) to create a package and noticed that the SQL statements created in the Preparation SQL Task only has code for creating tables. I want to make the package such that it first creates the destination database before creating all the related tables in it! When I tried to edit the SQL code to include DROP DATABASE and/or CREATE DATABASE statements, these were rejected.

Is it possible to do this or do I have to first create the database outside the package and then call the package? I want to make this a seamless process for clients who do not have the know-how of SQL Server database administration.

HELP!!!!!!

Can't you just run a CREATE DATABASE DDL statement in a execute sql task?

|||

Peter K wrote:

Can't you just run a CREATE DATABASE DDL statement in a execute sql task?

yes. i'm afraid that the import/export wizard won't be sufficient to solve this problem.