MIGRATE TO REPORTING SERVICE 2005

Good Morning,
I've a server mssql 2000 with reporting service and so also Visual
Studio.NET 2003.
Now I want to migrate to Reporting Service 2005,must I to upgrade also
Mssql to 2005 version and Visual Studio.NET 2005 or can I to upgrade
only Reporting Service?
ThanksYOu can upgrade Reporting Services without going to sql 2005... ( according
to Books On LIne)... Although we put the Reporting Services databases on an
instance of SQL 2005 - I don't think we had to...
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"Teo" wrote:
> Good Morning,
> I've a server mssql 2000 with reporting service and so also Visual
> Studio.NET 2003.
> Now I want to migrate to Reporting Service 2005,must I to upgrade also
> Mssql to 2005 version and Visual Studio.NET 2005 or can I to upgrade
> only Reporting Service?
> Thanks
>|||What is your current configuration? Local catalog (all on one server)?
Wayne is correct. You may install Reporting Services 2005 next to Reporting
Services 2000 and then use the 2005 Reporting Services Configuration Manager
to migrate your existing SQL2000 database to SQL2005... BOL is gray in the
fact that it appears that this is only supported in a remote catalog (SQL
and IIS on separate servers) configuration or a web farm/scale-out (multiple
IIS servers sharing a centralized SQL catalog) configuration but since
SQL2000 and SQL2005 can live on the same server it can be done on a local
catalog configuration... having said all that, unless you are needing to
maintain a SQL2000 environment for other reasons I don't see why you would
not want to upgrade you SQL2000 RDBMS to 2005, go for it!
--
Douglas McDowell douglas@.nospam.solidqualitylearning.com
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:3A2A647A-017C-442E-A1B9-D629DA7EEBEF@.microsoft.com...
> YOu can upgrade Reporting Services without going to sql 2005... (
> according
> to Books On LIne)... Although we put the Reporting Services databases on
> an
> instance of SQL 2005 - I don't think we had to...
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> I support the Professional Association for SQL Server ( PASS) and it''s
> community of SQL Professionals.
>
> "Teo" wrote:
>> Good Morning,
>> I've a server mssql 2000 with reporting service and so also Visual
>> Studio.NET 2003.
>> Now I want to migrate to Reporting Service 2005,must I to upgrade also
>> Mssql to 2005 version and Visual Studio.NET 2005 or can I to upgrade
>> only Reporting Service?
>> Thanks
>>|||My configuration is SQL Server and IIS on the same box. I upgraded only RS.
My SQL Server is still 2000 (note for all, you do have to have a SQL Server
2005 license if you do this). So, it is incorrect to say that this is only
supported with a remote catalog. That is definitely not true.
All you have to do when upgrading is select only RS 2005 when upgrading and
it all works.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Douglas McDowell" <douglas@.nospam.solidqualitylearning.com> wrote in
message news:e5L7GW7DGHA.2040@.TK2MSFTNGP14.phx.gbl...
> What is your current configuration? Local catalog (all on one server)?
> Wayne is correct. You may install Reporting Services 2005 next to
> Reporting Services 2000 and then use the 2005 Reporting Services
> Configuration Manager to migrate your existing SQL2000 database to
> SQL2005... BOL is gray in the fact that it appears that this is only
> supported in a remote catalog (SQL and IIS on separate servers)
> configuration or a web farm/scale-out (multiple IIS servers sharing a
> centralized SQL catalog) configuration but since SQL2000 and SQL2005 can
> live on the same server it can be done on a local catalog configuration...
> having said all that, unless you are needing to maintain a SQL2000
> environment for other reasons I don't see why you would not want to
> upgrade you SQL2000 RDBMS to 2005, go for it!
> --
> Douglas McDowell douglas@.nospam.solidqualitylearning.com
>
> "Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
> news:3A2A647A-017C-442E-A1B9-D629DA7EEBEF@.microsoft.com...
>> YOu can upgrade Reporting Services without going to sql 2005... (
>> according
>> to Books On LIne)... Although we put the Reporting Services databases on
>> an
>> instance of SQL 2005 - I don't think we had to...
>> --
>> Wayne Snyder MCDBA, SQL Server MVP
>> Mariner, Charlotte, NC
>> I support the Professional Association for SQL Server ( PASS) and it''s
>> community of SQL Professionals.
>>
>> "Teo" wrote:
>> Good Morning,
>> I've a server mssql 2000 with reporting service and so also Visual
>> Studio.NET 2003.
>> Now I want to migrate to Reporting Service 2005,must I to upgrade also
>> Mssql to 2005 version and Visual Studio.NET 2005 or can I to upgrade
>> only Reporting Service?
>> Thanks
>>
>|||But RS need Visual Studio.Net so if I want to install RS2005 , I must
to upgrade VS from version 2003 to 2005 ?
it's true?|||RS 2005 comes with a version of VS that is used for the report designer. You
can run side by side (leave your VS 2003 alone). If VS 2005 is installed
then RS 2005 will install the report designer to use that.
So, you do not need to purchase VS 2005.
Note that VS 2005 comes with two new controls for web and winforms. If you
want to use these new controls then you would need to upgrade VS.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Teo" <roninkaiser@.lycos.it> wrote in message
news:1136381218.597528.197920@.g43g2000cwa.googlegroups.com...
> But RS need Visual Studio.Net so if I want to install RS2005 , I must
> to upgrade VS from version 2003 to 2005 ?
> it's true?
>

migraiton from Analysis Service 2000 to 2005

I get this error during migraiton from Analysis Services 2000 to 2005

Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

IMRAN

Recently I successfully migrated OLAP database from 2000 to 2005 didn't see this error even I had to run few times migration wizards. Best guess, may be some thing not installed or configured correctly. However if you give at what step of migration you get this error that will help.

-Ashok

|||Databases:
FoodMart 2000
Data sources:
FoodMart
Dimensions:
Account
Category
Customer Pattern
Customers
Department
Education Level
Employees
Gender
HR^Pay Type
Marital Status
Position
Product
Promotion Media
Promotions
Store
Store Size in SQFT
Store Type
Time
Warehouse
Yearly Income
Years in the Company
Cubes:
Budget
HR
Sales
Trained Cube
Warehouse
Warehouse and Sales
Mining models:
Customer Pattern Discovery
Member Card RDBMS
Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).|||

Try upgrading your AS 2005 to SP2.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

migraiton from Analysis Service 2000 to 2005

I get this error during migraiton from Analysis Services 2000 to 2005

Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).

IMRAN

Recently I successfully migrated OLAP database from 2000 to 2005 didn't see this error even I had to run few times migration wizards. Best guess, may be some thing not installed or configured correctly. However if you give at what step of migration you get this error that will help.

-Ashok

|||Databases:
FoodMart 2000
Data sources:
FoodMart
Dimensions:
Account
Category
Customer Pattern
Customers
Department
Education Level
Employees
Gender
HR^Pay Type
Marital Status
Position
Product
Promotion Media
Promotions
Store
Store Size in SQFT
Store Type
Time
Warehouse
Yearly Income
Years in the Company
Cubes:
Budget
HR
Sales
Trained Cube
Warehouse
Warehouse and Sales
Mining models:
Customer Pattern Discovery
Member Card RDBMS
Unable to cast COM object of type 'System.__ComObject' to interface type 'Interop.Dso.IDbGroup90Ex'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{CE55E9E9-9597-4214-B21F-30C7683467B1}' failed due
to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).|||

Try upgrading your AS 2005 to SP2.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Microsoft.ReportingServices.UI ?

does microsoft give away the source for the reporting service ui?
usually installed in
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager\Pages
I would love to see the code for this page
<%@. Register TagPrefix="MSRS" Namespace="Microsoft.ReportingServices.UI"
Assembly="ReportingServicesWebUserInterface" %>
<%@. Page language="c#" Codebehind="DataSource.aspx.cs"
AutoEventWireup="false"
Inherits="Microsoft.ReportingServices.UI.DataSourcePage" %>
If they don't give this code away they should it would be very very helpfull.We all wish. But there is some sample UI code you can download.
--
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"letuce dance" <letucedance@.discussions.microsoft.com> wrote in message
news:8A7902B5-5496-458B-B323-013B9724EF53@.microsoft.com...
> does microsoft give away the source for the reporting service ui?
> usually installed in
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
> Services\ReportManager\Pages
> I would love to see the code for this page
> <%@. Register TagPrefix="MSRS" Namespace="Microsoft.ReportingServices.UI"
> Assembly="ReportingServicesWebUserInterface" %>
> <%@. Page language="c#" Codebehind="DataSource.aspx.cs"
> AutoEventWireup="false"
> Inherits="Microsoft.ReportingServices.UI.DataSourcePage" %>
> If they don't give this code away they should it would be very very
> helpfull.

Microsoft.AnalysisServices.AdomdClient.AdomdCacheExpiredException

Hello,

I have a asp.net application that connects to a cube in Analysis Service 2005 to do graphs. It's possible that other user might be using the same cube at the same time and make changes to the cube. If I use the graphing tol right after the cube is updated, I sometimes get an error message : "Microsoft.AnalysisServices.AdomdClient.AdomdCacheExpiredException : The Cubes collection has been updated on the server".

Is there a way to refresh the cache or refresh the cube collection? Any suggestion on how to handle this exception is appreciated.

Thank you,

Sincerely,

Annie

I beleive the better solution for the user in this case is to prompt your user to re-connect.

User session on the server has been disvalidated as a result of the some else's activity. To see consistent picture prompt your user to reconnect and refresh all the stuctures.
BTW this is behavior you would see in SQL Management Studio's Cube browser. The minute cube becomes invalid cube browser will asks you to re-connect.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Microsoft Update & SP1

Hi,
I recently upgraded to SQL Server 2005 SP1 (developer edition) on WinXP Pro
+ SP2 by using the Microsoft Update service.
No issues were noted during the upgrade process, and EXEC master..xp_msver
returns 9.00.2047.00 in the ProductVersion column.
However, subsequent running of Microsoft Update still shows SQL Server 2005
SP1 (KB913090) as needing to be installed.
Is this a bug with Microsoft Update, or does it mean that SP1 isn't
installed properly?
Any assistance gratefully received.
MarkHi Mark
It looks like you are on SP1 on that instance! Do you have multiple
instances on this machine? Did you check the installation's log files
(hopefully this is going to be in the same place as a manual installation!).
Have you rebooted since the upgrade?
If you are confident that it is upgraded then you could choose the option to
not show the update again when the update details are expanded.
John
"Mark Rae" wrote:

> Hi,
> I recently upgraded to SQL Server 2005 SP1 (developer edition) on WinXP Pr
o
> + SP2 by using the Microsoft Update service.
> No issues were noted during the upgrade process, and EXEC master..xp_msver
> returns 9.00.2047.00 in the ProductVersion column.
> However, subsequent running of Microsoft Update still shows SQL Server 200
5
> SP1 (KB913090) as needing to be installed.
> Is this a bug with Microsoft Update, or does it mean that SP1 isn't
> installed properly?
> Any assistance gratefully received.
> Mark
>
>|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:34B375F1-9334-4141-B282-2FB06C8D4A44@.microsoft.com...

> Do you have multiple instances on this machine?
No.

> Did you check the installation's log files (hopefully this is going to be
> in the same place as a manual installation!).
Yes.

> Have you rebooted since the upgrade?
Yes. And reapplied the upgrade. And rebooted after that.

> If you are confident that it is upgraded
I'm as confident as I can be, I suppose. Other than master..xp_msver /
SELECT @.@.VERSION, is there anything else I can try...?

> then you could choose the option to not show the update again
> when the update details are expanded.
Yes, but I was loathe to do that until I'd at least asked in here. I've done
a Google search, and there doesn't seem to be anything about this specific
issue. Lots about SP1, of course, but nothing relating to problems with
applying it through Microsoft Update.
I should receive SP1 on DVD any day now as part of my MSDN Universal
subscription, so I'll reinstall it from that and then remove the option from
Microsoft Update if that doesn't fix it.

Microsoft Update & SP1

Hi,
I recently upgraded to SQL Server 2005 SP1 (developer edition) on WinXP Pro
+ SP2 by using the Microsoft Update service.
No issues were noted during the upgrade process, and EXEC master..xp_msver
returns 9.00.2047.00 in the ProductVersion column.
However, subsequent running of Microsoft Update still shows SQL Server 2005
SP1 (KB913090) as needing to be installed.
Is this a bug with Microsoft Update, or does it mean that SP1 isn't
installed properly?
Any assistance gratefully received.
MarkHi Mark
It looks like you are on SP1 on that instance! Do you have multiple
instances on this machine? Did you check the installation's log files
(hopefully this is going to be in the same place as a manual installation!).
Have you rebooted since the upgrade?
If you are confident that it is upgraded then you could choose the option to
not show the update again when the update details are expanded.
John
"Mark Rae" wrote:
> Hi,
> I recently upgraded to SQL Server 2005 SP1 (developer edition) on WinXP Pro
> + SP2 by using the Microsoft Update service.
> No issues were noted during the upgrade process, and EXEC master..xp_msver
> returns 9.00.2047.00 in the ProductVersion column.
> However, subsequent running of Microsoft Update still shows SQL Server 2005
> SP1 (KB913090) as needing to be installed.
> Is this a bug with Microsoft Update, or does it mean that SP1 isn't
> installed properly?
> Any assistance gratefully received.
> Mark
>
>|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:34B375F1-9334-4141-B282-2FB06C8D4A44@.microsoft.com...
> Do you have multiple instances on this machine?
No.
> Did you check the installation's log files (hopefully this is going to be
> in the same place as a manual installation!).
Yes.
> Have you rebooted since the upgrade?
Yes. And reapplied the upgrade. And rebooted after that.
> If you are confident that it is upgraded
I'm as confident as I can be, I suppose. Other than master..xp_msver /
SELECT @.@.VERSION, is there anything else I can try...?
> then you could choose the option to not show the update again
> when the update details are expanded.
Yes, but I was loathe to do that until I'd at least asked in here. I've done
a Google search, and there doesn't seem to be anything about this specific
issue. Lots about SP1, of course, but nothing relating to problems with
applying it through Microsoft Update.
I should receive SP1 on DVD any day now as part of my MSDN Universal
subscription, so I'll reinstall it from that and then remove the option from
Microsoft Update if that doesn't fix it.