Default Folder for Deploying Projects

I have a real (hopefully) easy question...
I'm wanting to deploy a Reporting Services project to a particular folder on
my virtual server. For example, whenever you deploy a project it goes
straight to the home directory and creates the MODELS and DATA SOURCES
folders.
I would like to deploy my project to a folder I created called REPORTING
COMPONENTS.
Is this possible?
Thanks in advance for any help!!!Right mouse click, properties on the project. It brings up a property page
where you specify what you want it called on the server.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:1D246E5F-00EA-48CA-BC29-B6A661F0DD31@.microsoft.com...
>I have a real (hopefully) easy question...
> I'm wanting to deploy a Reporting Services project to a particular folder
> on
> my virtual server. For example, whenever you deploy a project it goes
> straight to the home directory and creates the MODELS and DATA SOURCES
> folders.
> I would like to deploy my project to a folder I created called REPORTING
> COMPONENTS.
> Is this possible?
> Thanks in advance for any help!!!|||I've tried that in the past and when I do I get the following error when
specifying any directory besides the default.
Here's where I want them to go:
http://10.90.160.13/ReportServerTest/Reporting Components:
Here's the error:
Client found response content type of '', but expected 'text/xml'.
The request failed with an empty response.
(Microsoft.ReportingServices.SemanticQueryDesign)
--
Program Location:
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String
methodname)
at
Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemType(String
Item)
at
Microsoft.ReportingServices.ModelDesigner.Project.ReportServiceClient.GetItemType(String item)
at
Microsoft.ReportingServices.ModelDesigner.Project.ReportServiceClient.CheckAuthorized()
at
Microsoft.ReportingServices.ModelDesigner.Project.ModelClientManager.GetCredentials(String url)
at
Microsoft.ReportingServices.ModelDesigner.Project.ModelProjectDeployer.PrepareDeploy()
"Bruce L-C [MVP]" wrote:
> Right mouse click, properties on the project. It brings up a property page
> where you specify what you want it called on the server.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:1D246E5F-00EA-48CA-BC29-B6A661F0DD31@.microsoft.com...
> >I have a real (hopefully) easy question...
> >
> > I'm wanting to deploy a Reporting Services project to a particular folder
> > on
> > my virtual server. For example, whenever you deploy a project it goes
> > straight to the home directory and creates the MODELS and DATA SOURCES
> > folders.
> >
> > I would like to deploy my project to a folder I created called REPORTING
> > COMPONENTS.
> >
> > Is this possible?
> >
> > Thanks in advance for any help!!!
>
>|||Is ReportServerTest the name of you reportserver directory? Usually this
would look like http://10.90.160.13/ReportServer/Reporting Components
RS creates two websites: ReportServer and Reports. Reports is the portal.
ReportServer is the asp.net application. Did you not install in the default
area?
You can specify the final directory, you cannot specify anything but
ReportServer (or whatever RS website is called).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:50DD68B4-C241-4068-B176-BB1D302862B6@.microsoft.com...
> I've tried that in the past and when I do I get the following error when
> specifying any directory besides the default.
> Here's where I want them to go:
> http://10.90.160.13/ReportServerTest/Reporting Components:
> Here's the error:
> Client found response content type of '', but expected 'text/xml'.
> The request failed with an empty response.
> (Microsoft.ReportingServices.SemanticQueryDesign)
> --
> Program Location:
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String
> methodname)
> at
> Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemType(String
> Item)
> at
> Microsoft.ReportingServices.ModelDesigner.Project.ReportServiceClient.GetItemType(String
> item)
> at
> Microsoft.ReportingServices.ModelDesigner.Project.ReportServiceClient.CheckAuthorized()
> at
> Microsoft.ReportingServices.ModelDesigner.Project.ModelClientManager.GetCredentials(String
> url)
> at
> Microsoft.ReportingServices.ModelDesigner.Project.ModelProjectDeployer.PrepareDeploy()
>
> "Bruce L-C [MVP]" wrote:
>> Right mouse click, properties on the project. It brings up a property
>> page
>> where you specify what you want it called on the server.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
>> news:1D246E5F-00EA-48CA-BC29-B6A661F0DD31@.microsoft.com...
>> >I have a real (hopefully) easy question...
>> >
>> > I'm wanting to deploy a Reporting Services project to a particular
>> > folder
>> > on
>> > my virtual server. For example, whenever you deploy a project it goes
>> > straight to the home directory and creates the MODELS and DATA SOURCES
>> > folders.
>> >
>> > I would like to deploy my project to a folder I created called
>> > REPORTING
>> > COMPONENTS.
>> >
>> > Is this possible?
>> >
>> > Thanks in advance for any help!!!
>>|||I eventually figured it out... :-)
There are three properties: target folderr for models, data sources, and
URL. I was modifying the URL...no no no!!!
I modified the target folders and everything is peachy...
Thanks for your help Bruce...!
"Bruce L-C [MVP]" wrote:
> Right mouse click, properties on the project. It brings up a property page
> where you specify what you want it called on the server.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:1D246E5F-00EA-48CA-BC29-B6A661F0DD31@.microsoft.com...
> >I have a real (hopefully) easy question...
> >
> > I'm wanting to deploy a Reporting Services project to a particular folder
> > on
> > my virtual server. For example, whenever you deploy a project it goes
> > straight to the home directory and creates the MODELS and DATA SOURCES
> > folders.
> >
> > I would like to deploy my project to a folder I created called REPORTING
> > COMPONENTS.
> >
> > Is this possible?
> >
> > Thanks in advance for any help!!!
>
>

default DB names for SSRS?

I was wondering if one SQL Server could host more then one set of Reporting Services databases? This would then lead to the question of, can the default names be change to what ever? Say the Accounting and R/D groups wants to use the same SSRS so, we name their databases ACCT_ReportServer and RD_ReportServer, etc..? Can I do this? I believe I can but need to be sure.

thanks much,
joe

can i ask , why you would want to do this? Report Server allows you to set up groups of people who have access to certain reports...

sound to me like it would be a waste of resources to have multiple ssrs databases... besides I honestly don't think it would work.

Report server security feature is very good, that is the only reason I can think of why you might want to seperate them.

|||Thanks for you quick reply. I really do need to do more reading/research. As long as I can keep groups separated, that will work.

Again - Thanks.
|||Hey JoeyDba,
How's it going today? Did you find any more answers?

Debugging while running reporting services

I am attempting to debug a customer security dll that is called by Reporting Services. The DLL works great and functions correctly. I am trying to set breakpoints in the code, but they are ignored. I changed the web.config for ReportManager and ReportServer to set debug=true. However, still no luck. The application never stops, it just works.

I have tried this on a Windows XP Pro with no luck. Any suggestions?

Are you debugging the asp.net worker process? Did you configure VS to point to the correct symbols?

-Daniel

Debugging SQL statement

I am working in SQL Server Reporting Services, and I have an error using a dynamic parameter. The error surfaces during runtime. I believe I could fix the parameter if I knew exactly what the resulting SQL statement looks like. So the question is: how do I view the actual SQL statement that is being executed in a report? I tried SQL Profiler, which shows how my parameter drop-down lists are being populated, but it does not show the main dataset SQL statement.

Alternatively, are there any examples of using a dynamic parameter that is a "datetime" data type?

Any help would be appreciated. Thanks.

Hello,

When are you getting the error, after setting your parameters when you click "View Report"?

You should be capturing the 'Exception' and 'SQL:BatchStarting' events in your trace. This will first whenever the report is started (regardless of error) and any error from the SQL statement.

Of course, if you have the RDL file, you can always look in there for the SQL command under the <CommandText> tag.

Hope this helps.

Jarret

|||

Thanks for responding.

Yes, I am getting the error after I click "View Report". I have the RDL file, but next to the <CommandText> tag, I see the same statement construct that I used in the Dataset (i.e. I see the IIf(parameter!... structure instead of an actual SQL statement) . I'll check out the trace again, but I'm certain that the only SQL statements that were in there pertain to setting up the parameter lists (e.g. "select salesrep from sourcetable").

Thanks again.

|||

Were you able to set up the trace and see the exception and the main dataset's SQL statement? Do you get the error when you're in BIDS using the preview tab? If so, you should be able to see the error (it may be in the output window, Ctrl+Alt+O).

If you have multiple dataset's there should be a <CommandText> tag for each one in your RDL file. Inside of each of these should be the SQL query. Are you saying you have references to Parameters!... in your dataset? Your dataset command should only contain a valid SQL statement, as this is what is sent to the DB server to be executed.

Go to the data tab in BIDS and select your main dataset from the 'Dataset:' dropdown. It should load that command (from the RDL file), then hit the red Exclamation button to run the query. Do you get an error?

Jarret

Debugging a customponent used in a Integration Services project

Hi there
I'm building a SQL Server integration services project with a custom component. I created the custom component as a separate C# library project and compiled it. With the help of some online resources I was able to make it appear in the Dataflow Transformations toolbox items of Integration Services IDE. But this component is throwing some errors. My question how do I setup the environment such that I can set break points and debug the component's source while debugging the integration services project?

Any help will be greatly appretiated.

Thanks in advance.

Arun M

Hi Arun,

open the SSIS designer with your component in it, open another VS window with your C# project where you would like to debug. For design-time debugging, attach the VS debugger (using Debug\Attach to Process...) to devenv.exe process that hosts the SSIS designer. For runtime debugging, attach your debugger to DtsDebugHost.exe.

HTH.

Thanks,

|||Here's another way to debug things, a little different than the way Bob suggested above:

Setup the Custom task to run using DTEXEC as it's startup
program. In the CommandLine arguments, pass in the
filename of the DTSX package that includes the custom
task. Then start the debugger and it should hit your
breakpoints...|||

I am trying to use the second method of DTEXEC but I am getting a "The product level is insufficient for component ..." message on one of my machines and ONLY ONE of them.

The notable difference is that I am connecting to my local machine running the databases VS a remote database. The one using the remote database is failing with the above message and the local database machine debugs just fine.

Note: Running the package with the custom component through VS works just fine.

I am going to attempt the DtsHost... item above but I don't like that one as you have to close the VS environment over and over to do testing of changes!

|||This issue has already been discussed in this forum. To use dtexec you must have a server OS.|||

Then why would I get one working and not the other when they are both on Windows XP SP2?

Is it that DTEXEC can only connect remotely while on a server OS? That seems rather strange to me...

|||No you must have installed SSIS. DTEXEC runs fine on all OS's that SSIS runs on, which includes XP. The message is usally encountered when using the Wizard, and only having installed workstation components, and not the SSIS server components.|||

I am pretty sure I have it all installed and not just the workstation components as I am developing and running on the machine itself.

The component runs fine in BIDS both at design and run-time but only fails with the message when I try to run using DTEXEC.

Darren: Thank you for the pointer to the Regex example that was recently released. I am building a component that will use Regex to allow validation with custom messages logged, data type reformatting based on the matches (e.g. yyyyMMdd -> ^(\d{4})(\d{2})(\d{2})$ would validate the data and $1-$2-$3 would convert the data to a data string that can be type cast to DT_DBTIMESTAMP). Makes the date conversion much simpler.

Debugging a customponent used in a Integration Services project

Hi there
I'm building a SQL Server integration services project with a custom component. I created the custom component as a separate C# library project and compiled it. With the help of some online resources I was able to make it appear in the Dataflow Transformations toolbox items of Integration Services IDE. But this component is throwing some errors. My question how do I setup the environment such that I can set break points and debug the component's source while debugging the integration services project?

Any help will be greatly appretiated.

Thanks in advance.

Arun M

Hi Arun,

open the SSIS designer with your component in it, open another VS window with your C# project where you would like to debug. For design-time debugging, attach the VS debugger (using Debug\Attach to Process...) to devenv.exe process that hosts the SSIS designer. For runtime debugging, attach your debugger to DtsDebugHost.exe.

HTH.

Thanks,

|||Here's another way to debug things, a little different than the way Bob suggested above:

Setup the Custom task to run using DTEXEC as it's startup
program. In the CommandLine arguments, pass in the
filename of the DTSX package that includes the custom
task. Then start the debugger and it should hit your
breakpoints...
|||

I am trying to use the second method of DTEXEC but I am getting a "The product level is insufficient for component ..." message on one of my machines and ONLY ONE of them.

The notable difference is that I am connecting to my local machine running the databases VS a remote database. The one using the remote database is failing with the above message and the local database machine debugs just fine.

Note: Running the package with the custom component through VS works just fine.

I am going to attempt the DtsHost... item above but I don't like that one as you have to close the VS environment over and over to do testing of changes!

|||This issue has already been discussed in this forum. To use dtexec you must have a server OS.
|||

Then why would I get one working and not the other when they are both on Windows XP SP2?

Is it that DTEXEC can only connect remotely while on a server OS? That seems rather strange to me...

|||No you must have installed SSIS. DTEXEC runs fine on all OS's that SSIS runs on, which includes XP. The message is usally encountered when using the Wizard, and only having installed workstation components, and not the SSIS server components.|||

I am pretty sure I have it all installed and not just the workstation components as I am developing and running on the machine itself.

The component runs fine in BIDS both at design and run-time but only fails with the message when I try to run using DTEXEC.

Darren: Thank you for the pointer to the Regex example that was recently released. I am building a component that will use Regex to allow validation with custom messages logged, data type reformatting based on the matches (e.g. yyyyMMdd -> ^(\d{4})(\d{2})(\d{2})$ would validate the data and $1-$2-$3 would convert the data to a data string that can be type cast to DT_DBTIMESTAMP). Makes the date conversion much simpler.

Death of ODBC

ODBC is not supported as a data source in SQL Analysis Services 2005.

ODBC is not supported as a data source in SQL Reporting Services 2005 Model Designer.

Any thoughts?

Joe

Don't read too much into this, ODBC is not going away anytime soon. We put a lot of effort into SQL Native Client, which contains the ODBC driver for SQL Server 2005.

|||Chris,
But I must use ODBC to connect to a Progress database - not SQL Server. There does not seem to be any way to accomplish this in Analysis Services 2005 or the RS Model Designer.|||

With regard to Model builder - in SQL Server 2005 Reporting Services supports building models on top of Analysis Services and SQL Server 2005 and SQL Server 2000 data source.

This is not to be read as a 'death of ODBC', rather it reflects the significant effort required to support a particular data source for semantic modeling purposes. Essentially what Reporting Services does under the covers is:
1) Evaluates the schema and content of the data source to determine what entities, attributes, and roles (relationships) exist. It also looks at how much data is in the tables, and applies some heuristics based on patterns in the data to determine a good best guess as to what the model should look like.
2) Once you have a model, RS translates from semantic queries into underlying data source queries. In doing so we have dependencies on the behavior (and existence) of query language specific functions.

Between these two things, there is a ton of potential failures across an interface like ODBC - we don't know if the underlying data source supports the actions we're going to try to perform. If we let you do this, it would lead to a very fragile system with many uncertain behaviors. As such we decided to limit the set of data sources that are supported in SQL Server 2005 to AS and SQL 2005 and SQL 2000.

Hope that helps,

-Lukasz

|||Lukasz,

Thanks for your reply. I can see from your explanation that it's not easy to support ODBC in the Model Designer.
- Are there any plans to support ODBC in the future?
If not then as far as the Model Designer goes - ODBC is dead.

What I find even more worrying is that SSAS 2005 does not support ODBC - there must be users out there who have developed a solution in SSAS 2000 & ODBC who will want to upgrade.

Don't get me wrong - I think the Model Designer, etc. are fantastic - I just wish I worked for a company who used SQL Server! All this ODBC stuff is getting me down...|||

Hey DillanJoe

I'm attempting to use ssas 2005 to connect to a postgres database did you have any luck connecting via ODBC?

Cheers

|||

kiwi,

I've not looked at SSAS for many months and I have not had any luck using ODBC with it. If you make some progress please post here!

Good luck

|||

Hi Lucaz

Will a .net data provider work better then ODBC (eg http://crlab.com/pgsqlnet/download.html).

my customer wants to buid and query report Builder 2005 models against a Postgress data base.

Regards..Yasin

Auckland, New Zealand

|||

Hi Yasin

Have you had any luck with this product, it looks like a good option.

Derek

|||

Hi Derek,

No, not yet. The customer is thinking over it. We might do the linked server option. Then build all the Primary keys/FK's on the FE (SQL server end).

Ping me in a month and I will let you know.

Regards ..Yasin

|||

Hi,

I am facing a problem connecting to a progress db from .net 2005, when i test the connection, (odbc) is says fine (successful)., then when i try connecting it says connection string is not correct.,

any one knows a driver update or something?

Death of ODBC

ODBC is not supported as a data source in SQL Analysis Services 2005.

ODBC is not supported as a data source in SQL Reporting Services 2005 Model Designer.

Any thoughts?

Joe

Don't read too much into this, ODBC is not going away anytime soon. We put a lot of effort into SQL Native Client, which contains the ODBC driver for SQL Server 2005.

|||Chris,
But I must use ODBC to connect to a Progress database - not SQL Server. There does not seem to be any way to accomplish this in Analysis Services 2005 or the RS Model Designer.|||

With regard to Model builder - in SQL Server 2005 Reporting Services supports building models on top of Analysis Services and SQL Server 2005 and SQL Server 2000 data source.

This is not to be read as a 'death of ODBC', rather it reflects the significant effort required to support a particular data source for semantic modeling purposes. Essentially what Reporting Services does under the covers is:
1) Evaluates the schema and content of the data source to determine what entities, attributes, and roles (relationships) exist. It also looks at how much data is in the tables, and applies some heuristics based on patterns in the data to determine a good best guess as to what the model should look like.
2) Once you have a model, RS translates from semantic queries into underlying data source queries. In doing so we have dependencies on the behavior (and existence) of query language specific functions.

Between these two things, there is a ton of potential failures across an interface like ODBC - we don't know if the underlying data source supports the actions we're going to try to perform. If we let you do this, it would lead to a very fragile system with many uncertain behaviors. As such we decided to limit the set of data sources that are supported in SQL Server 2005 to AS and SQL 2005 and SQL 2000.

Hope that helps,

-Lukasz

|||Lukasz,

Thanks for your reply. I can see from your explanation that it's not easy to support ODBC in the Model Designer.
- Are there any plans to support ODBC in the future?
If not then as far as the Model Designer goes - ODBC is dead.

What I find even more worrying is that SSAS 2005 does not support ODBC - there must be users out there who have developed a solution in SSAS 2000 & ODBC who will want to upgrade.

Don't get me wrong - I think the Model Designer, etc. are fantastic - I just wish I worked for a company who used SQL Server! All this ODBC stuff is getting me down...|||

Hey DillanJoe

I'm attempting to use ssas 2005 to connect to a postgres database did you have any luck connecting via ODBC?

Cheers

|||

kiwi,

I've not looked at SSAS for many months and I have not had any luck using ODBC with it. If you make some progress please post here!

Good luck

|||

Hi Lucaz

Will a .net data provider work better then ODBC (eg http://crlab.com/pgsqlnet/download.html).

my customer wants to buid and query report Builder 2005 models against a Postgress data base.

Regards..Yasin

Auckland, New Zealand

|||

Hi Yasin

Have you had any luck with this product, it looks like a good option.

Derek

|||

Hi Derek,

No, not yet. The customer is thinking over it. We might do the linked server option. Then build all the Primary keys/FK's on the FE (SQL server end).

Ping me in a month and I will let you know.

Regards ..Yasin

|||

Hi,

I am facing a problem connecting to a progress db from .net 2005, when i test the connection, (odbc) is says fine (successful)., then when i try connecting it says connection string is not correct.,

any one knows a driver update or something?

Death of ODBC

ODBC is not supported as a data source in SQL Analysis Services 2005.

ODBC is not supported as a data source in SQL Reporting Services 2005 Model Designer.

Any thoughts?

Joe

Don't read too much into this, ODBC is not going away anytime soon. We put a lot of effort into SQL Native Client, which contains the ODBC driver for SQL Server 2005.

|||Chris,
But I must use ODBC to connect to a Progress database - not SQL Server. There does not seem to be any way to accomplish this in Analysis Services 2005 or the RS Model Designer.|||

With regard to Model builder - in SQL Server 2005 Reporting Services supports building models on top of Analysis Services and SQL Server 2005 and SQL Server 2000 data source.

This is not to be read as a 'death of ODBC', rather it reflects the significant effort required to support a particular data source for semantic modeling purposes. Essentially what Reporting Services does under the covers is:
1) Evaluates the schema and content of the data source to determine what entities, attributes, and roles (relationships) exist. It also looks at how much data is in the tables, and applies some heuristics based on patterns in the data to determine a good best guess as to what the model should look like.
2) Once you have a model, RS translates from semantic queries into underlying data source queries. In doing so we have dependencies on the behavior (and existence) of query language specific functions.

Between these two things, there is a ton of potential failures across an interface like ODBC - we don't know if the underlying data source supports the actions we're going to try to perform. If we let you do this, it would lead to a very fragile system with many uncertain behaviors. As such we decided to limit the set of data sources that are supported in SQL Server 2005 to AS and SQL 2005 and SQL 2000.

Hope that helps,

-Lukasz

|||Lukasz,

Thanks for your reply. I can see from your explanation that it's not easy to support ODBC in the Model Designer.
- Are there any plans to support ODBC in the future?
If not then as far as the Model Designer goes - ODBC is dead.

What I find even more worrying is that SSAS 2005 does not support ODBC - there must be users out there who have developed a solution in SSAS 2000 & ODBC who will want to upgrade.

Don't get me wrong - I think the Model Designer, etc. are fantastic - I just wish I worked for a company who used SQL Server! All this ODBC stuff is getting me down...|||

Hey DillanJoe

I'm attempting to use ssas 2005 to connect to a postgres database did you have any luck connecting via ODBC?

Cheers

|||

kiwi,

I've not looked at SSAS for many months and I have not had any luck using ODBC with it. If you make some progress please post here!

Good luck

|||

Hi Lucaz

Will a .net data provider work better then ODBC (eg http://crlab.com/pgsqlnet/download.html).

my customer wants to buid and query report Builder 2005 models against a Postgress data base.

Regards..Yasin

Auckland, New Zealand

|||

Hi Yasin

Have you had any luck with this product, it looks like a good option.

Derek

|||

Hi Derek,

No, not yet. The customer is thinking over it. We might do the linked server option. Then build all the Primary keys/FK's on the FE (SQL server end).

Ping me in a month and I will let you know.

Regards ..Yasin

|||

Hi,

I am facing a problem connecting to a progress db from .net 2005, when i test the connection, (odbc) is says fine (successful)., then when i try connecting it says connection string is not correct.,

any one knows a driver update or something?

Death of ODBC

ODBC is not supported as a data source in SQL Analysis Services 2005.

ODBC is not supported as a data source in SQL Reporting Services 2005 Model Designer.

Any thoughts?

Joe

Don't read too much into this, ODBC is not going away anytime soon. We put a lot of effort into SQL Native Client, which contains the ODBC driver for SQL Server 2005.

|||Chris,
But I must use ODBC to connect to a Progress database - not SQL Server. There does not seem to be any way to accomplish this in Analysis Services 2005 or the RS Model Designer.|||

With regard to Model builder - in SQL Server 2005 Reporting Services supports building models on top of Analysis Services and SQL Server 2005 and SQL Server 2000 data source.

This is not to be read as a 'death of ODBC', rather it reflects the significant effort required to support a particular data source for semantic modeling purposes. Essentially what Reporting Services does under the covers is:
1) Evaluates the schema and content of the data source to determine what entities, attributes, and roles (relationships) exist. It also looks at how much data is in the tables, and applies some heuristics based on patterns in the data to determine a good best guess as to what the model should look like.
2) Once you have a model, RS translates from semantic queries into underlying data source queries. In doing so we have dependencies on the behavior (and existence) of query language specific functions.

Between these two things, there is a ton of potential failures across an interface like ODBC - we don't know if the underlying data source supports the actions we're going to try to perform. If we let you do this, it would lead to a very fragile system with many uncertain behaviors. As such we decided to limit the set of data sources that are supported in SQL Server 2005 to AS and SQL 2005 and SQL 2000.

Hope that helps,

-Lukasz

|||Lukasz,

Thanks for your reply. I can see from your explanation that it's not easy to support ODBC in the Model Designer.
- Are there any plans to support ODBC in the future?
If not then as far as the Model Designer goes - ODBC is dead.

What I find even more worrying is that SSAS 2005 does not support ODBC - there must be users out there who have developed a solution in SSAS 2000 & ODBC who will want to upgrade.

Don't get me wrong - I think the Model Designer, etc. are fantastic - I just wish I worked for a company who used SQL Server! All this ODBC stuff is getting me down...|||

Hey DillanJoe

I'm attempting to use ssas 2005 to connect to a postgres database did you have any luck connecting via ODBC?

Cheers

|||

kiwi,

I've not looked at SSAS for many months and I have not had any luck using ODBC with it. If you make some progress please post here!

Good luck

|||

Hi Lucaz

Will a .net data provider work better then ODBC (eg http://crlab.com/pgsqlnet/download.html).

my customer wants to buid and query report Builder 2005 models against a Postgress data base.

Regards..Yasin

Auckland, New Zealand

|||

Hi Yasin

Have you had any luck with this product, it looks like a good option.

Derek

|||

Hi Derek,

No, not yet. The customer is thinking over it. We might do the linked server option. Then build all the Primary keys/FK's on the FE (SQL server end).

Ping me in a month and I will let you know.

Regards ..Yasin

|||

Hi,

I am facing a problem connecting to a progress db from .net 2005, when i test the connection, (odbc) is says fine (successful)., then when i try connecting it says connection string is not correct.,

any one knows a driver update or something?