Mirroring between Standard and Enterprise editions...

Hi All,

We are going to use database mirroring and database snapshots for reporting. The principal server runs SQL Server 2005 Standard Edition and mirror (reporting) runs SQL Server 2005 Enterprise Edition (64-bit). I failed to setup database mirroring trough GUI using SQL Server Management Studio and got this error:

This mirroring configuration is not supported. Because the principal server instance, <server_name>, is Standard Edition, the mirror server instance must also be Standard Edition.

But when I use T-SQL commands I was able to setup database mirroring and it works OK so far.

SQL BOL says that one of requirements for database mirroring is to use the same SQL Server editions but I am wondering if it works trough T-SQL why MS mention it in the requirements list, also is totally unsupported by MS?

Thanks

Oleg

Oleg,

While this will probably work fine, we don't test this combination internally. If you mirror from a principal that is STD edition to a mirror that is EE edition, it would probably work without issues. Mirroring the other way (from EE to STD) could be problematic because of the EE features that are not present in STD. Since mirroring supports failover and failback, in theory it is possible for you to be in the situation where you are mirroring from EE->STD edition even if that is not the initial configuarion.

Regards,

Matt Hollingsworth

Program Manager, SQL Server High Availability

|||

Matt,

Thanks for your answer.

Our plan is to use database mirroring only for reporting and not for high availability. (We use replication and remote DC for HA). So mirroring from Standard to Enterprise Edition will be the only one scenario that we going to use option in our reporting environment.
The concern that we have is if we will be able to use mirroring between Standard and Enterprise in the future releases of SP2, SP3.

Thanks Oleg

|||

I am curious to why you want EE on the mirror server?

Only because the database snapshot feature?

Actually this is very similiar to what we need (use mirroring mostly for reports, not for HA) but since we don't have EE, we actually setup 2 STD instances on the mirror server

Server1 <- live server

Server2\Mirror <- mirrored, can be automatic fail over

Server2\Log <- log shipping, used for reports

Server3 <- witness and log shipping monitor server

Although I do recall seeing someone mention that we do not need a license if only using the mirror server in standby mode

Does that mean we can use EE with snapshot on Server2 without having to pay a license?

Thanks

|||

Yes we are going to use EE edition only for reporting since it doesn't require extra support efforts and also we can have a fair data refresh latency.
For the stand-by server you don't have to pay for licensing and it's valid for cluster or mirroring unless you also going to use it also for reporting.

tnx.

I'm closing this topic, thanks to all for answers and inputs............OH

|||

>> Although I do recall seeing someone mention that we do not need a license if only using the mirror server in standby mode

No, it doesn't. This only applies if you are using the 2nd server for failover only. By creating snapshots and running reporting off of it, it is no longer a failover only server.

Also, in order to cover both servers under 1 license, the license has to be valid for each server. So, you would have to run both under an Enterprise license, not a standard license.

Mirroring between Standard and Enterprise editions...

Hi All,

We are going to use database mirroring and database snapshots for reporting. The principal server runs SQL Server 2005 Standard Edition and mirror (reporting) runs SQL Server 2005 Enterprise Edition (64-bit). I failed to setup database mirroring trough GUI using SQL Server Management Studio and got this error:

This mirroring configuration is not supported. Because the principal server instance, <server_name>, is Standard Edition, the mirror server instance must also be Standard Edition.

But when I use T-SQL commands I was able to setup database mirroring and it works OK so far.

SQL BOL says that one of requirements for database mirroring is to use the same SQL Server editions but I am wondering if it works trough T-SQL why MS mention it in the requirements list, also is totally unsupported by MS?

Thanks

Oleg

Oleg,

While this will probably work fine, we don't test this combination internally. If you mirror from a principal that is STD edition to a mirror that is EE edition, it would probably work without issues. Mirroring the other way (from EE to STD) could be problematic because of the EE features that are not present in STD. Since mirroring supports failover and failback, in theory it is possible for you to be in the situation where you are mirroring from EE->STD edition even if that is not the initial configuarion.

Regards,

Matt Hollingsworth

Program Manager, SQL Server High Availability

|||

Matt,

Thanks for your answer.

Our plan is to use database mirroring only for reporting and not for high availability. (We use replication and remote DC for HA). So mirroring from Standard to Enterprise Edition will be the only one scenario that we going to use option in our reporting environment.
The concern that we have is if we will be able to use mirroring between Standard and Enterprise in the future releases of SP2, SP3.

Thanks Oleg

|||

I am curious to why you want EE on the mirror server?

Only because the database snapshot feature?

Actually this is very similiar to what we need (use mirroring mostly for reports, not for HA) but since we don't have EE, we actually setup 2 STD instances on the mirror server

Server1 <- live server

Server2\Mirror <- mirrored, can be automatic fail over

Server2\Log <- log shipping, used for reports

Server3 <- witness and log shipping monitor server

Although I do recall seeing someone mention that we do not need a license if only using the mirror server in standby mode

Does that mean we can use EE with snapshot on Server2 without having to pay a license?

Thanks

|||

Yes we are going to use EE edition only for reporting since it doesn't require extra support efforts and also we can have a fair data refresh latency.
For the stand-by server you don't have to pay for licensing and it's valid for cluster or mirroring unless you also going to use it also for reporting.

tnx.

I'm closing this topic, thanks to all for answers and inputs............OH

|||

>> Although I do recall seeing someone mention that we do not need a license if only using the mirror server in standby mode

No, it doesn't. This only applies if you are using the 2nd server for failover only. By creating snapshots and running reporting off of it, it is no longer a failover only server.

Also, in order to cover both servers under 1 license, the license has to be valid for each server. So, you would have to run both under an Enterprise license, not a standard license.

mirror db blocking issue

Hello All
I've set up a job to backup our financial db and restore it to the same
machine (different files & db name) for reporting. This was to avoid a
blocking issue caused by the front end financial system.
The thing is, the blocking is still there, even when you are reporting
on the mirror database and the blocking process is on the other db!
Is this something to do with the objects having the same names/indexes
in sysobjects? Any ideas on how to resolve it?
Thanks!
Paul
That isn't possible. I suspect you have more to this than you are reporting.
Locks in one db do not affect queries in another unless the query or
transaction is across both dbs. You might want to have a look at these:
http://support.microsoft.com/kb/271509
http://www.sql-server-performance.com/sf_block_prevention.asp
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165263399.585739.293410@.16g2000cwy.googlegro ups.com...
> Hello All
> I've set up a job to backup our financial db and restore it to the same
> machine (different files & db name) for reporting. This was to avoid a
> blocking issue caused by the front end financial system.
> The thing is, the blocking is still there, even when you are reporting
> on the mirror database and the blocking process is on the other db!
> Is this something to do with the objects having the same names/indexes
> in sysobjects? Any ideas on how to resolve it?
> Thanks!
> Paul
>
|||You are absolutely right, I was being a dumb-XXX
I had the dbname hardcoded in the stored procedures
Thsnks for your time though!
P
|||That is the biggest argument to never using the db name in the object
qualifier unless you are actually intending to go cross db in the first
place. You are not the first one to get bit by that and you won't be the
last.
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165316471.090188.94890@.16g2000cwy.googlegrou ps.com...
> You are absolutely right, I was being a dumb-XXX
> I had the dbname hardcoded in the stored procedures
> Thsnks for your time though!
> P
>
sql

mirror db blocking issue

Hello All
I've set up a job to backup our financial db and restore it to the same
machine (different files & db name) for reporting. This was to avoid a
blocking issue caused by the front end financial system.
The thing is, the blocking is still there, even when you are reporting
on the mirror database and the blocking process is on the other db!
Is this something to do with the objects having the same names/indexes
in sysobjects? Any ideas on how to resolve it?
Thanks!
PaulThat isn't possible. I suspect you have more to this than you are reporting.
Locks in one db do not affect queries in another unless the query or
transaction is across both dbs. You might want to have a look at these:
http://support.microsoft.com/kb/271509
http://www.sql-server-performance.com/sf_block_prevention.asp
--
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165263399.585739.293410@.16g2000cwy.googlegroups.com...
> Hello All
> I've set up a job to backup our financial db and restore it to the same
> machine (different files & db name) for reporting. This was to avoid a
> blocking issue caused by the front end financial system.
> The thing is, the blocking is still there, even when you are reporting
> on the mirror database and the blocking process is on the other db!
> Is this something to do with the objects having the same names/indexes
> in sysobjects? Any ideas on how to resolve it?
> Thanks!
> Paul
>|||You are absolutely right, I was being a dumb-ass
I had the dbname hardcoded in the stored procedures
Thsnks for your time though!
P|||That is the biggest argument to never using the db name in the object
qualifier unless you are actually intending to go cross db in the first
place. You are not the first one to get bit by that and you won't be the
last.
--
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165316471.090188.94890@.16g2000cwy.googlegroups.com...
> You are absolutely right, I was being a dumb-ass
> I had the dbname hardcoded in the stored procedures
> Thsnks for your time though!
> P
>

mirror db blocking issue

Hello All
I've set up a job to backup our financial db and restore it to the same
machine (different files & db name) for reporting. This was to avoid a
blocking issue caused by the front end financial system.
The thing is, the blocking is still there, even when you are reporting
on the mirror database and the blocking process is on the other db!
Is this something to do with the objects having the same names/indexes
in sysobjects? Any ideas on how to resolve it?
Thanks!
PaulThat isn't possible. I suspect you have more to this than you are reporting.
Locks in one db do not affect queries in another unless the query or
transaction is across both dbs. You might want to have a look at these:
http://support.microsoft.com/kb/271509
http://www.sql-server-performance.c..._prevention.asp
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165263399.585739.293410@.16g2000cwy.googlegroups.com...
> Hello All
> I've set up a job to backup our financial db and restore it to the same
> machine (different files & db name) for reporting. This was to avoid a
> blocking issue caused by the front end financial system.
> The thing is, the blocking is still there, even when you are reporting
> on the mirror database and the blocking process is on the other db!
> Is this something to do with the objects having the same names/indexes
> in sysobjects? Any ideas on how to resolve it?
> Thanks!
> Paul
>|||You are absolutely right, I was being a dumb-XXX
I had the dbname hardcoded in the stored procedures
Thsnks for your time though!
P|||That is the biggest argument to never using the db name in the object
qualifier unless you are actually intending to go cross db in the first
place. You are not the first one to get bit by that and you won't be the
last.
Andrew J. Kelly SQL MVP
"pdm" <paulusm@.gmail.com> wrote in message
news:1165316471.090188.94890@.16g2000cwy.googlegroups.com...
> You are absolutely right, I was being a dumb-XXX
> I had the dbname hardcoded in the stored procedures
> Thsnks for your time though!
> P
>

Mining Model Parameter

I have one main mining structure and several mining models that are using the MS Decision Trees algorithm. I have a Reporting Services report that displays the model using a table. I want to set it up so that in the DMX query, I can use a parameter to specify which model to use. That way I just have one report that can reference multiple models. For example I would like to do something like this:

SELECT FLATTENED * FROM [@.model].CONTENT

This doesn't work because I get the error message:

Preparation of DMX query failed.
Error (Data mining): Either the user, user, does not have permission to access the referenced mining model, @.model, or the object does not exist. (Microsoft SQL Server 2005 Analysis Services)

We are running SSAS 2005 SP2. Is there a way to accomplish this?

DMX does not support parameterization of the name of the object being queried.
One of the reasons is that a statement, once prepared, is supposed to have a well defined response schema (column definition) and this cannot be enforced as the value of the parameter changes. For example, the query above would return various results depending on the model being queried.

That aside, you should be able to construct the query by concatenating the DMX fragments with the report parameter, something like
"SELECT FLATTENED * FROM [" + @.model + "].CONTENT"|||

Thanks for your response. I actually tried that and it didn't seem to work. But I did figure out a way to do it. I created a stored procedure that looks like this:

Code Snippet

AS

BEGIN

DECLARE @.OPENQUERY nvarchar(4000), @.TSQL nvarchar(4000), @.LinkedServer nvarchar(4000)

SET @.LinkedServer = 'DMSERVER'

SET @.OPENQUERY = 'SELECT * FROM OPENQUERY('+ @.LinkedServer + ','''

SET @.TSQL = 'SELECT FLATTENED * FROM ['+@.miningModel+'].CONTENT'')'

EXEC (@.OPENQUERY+@.TSQL)

END

The linked server connects to the instance of SSAS 2005 and then I just call the stored procedure from reporting services and pass in the miningModel variable. I had to set it up this way becase OPENQUERY doesn't accept variables for its arguements. I found this article that explains how to get around it. You'll see that I just copied what they did. It might be a little bit of a hack but it works!

Minimum version of Visual Studio.NET

What is the minimum requirement or version of Visual Studio.NET
necessary for editing reports when running Reporting Services. I am
running on a SQL 2000 sp3 and Windows 2003 server.Anything that comes with VS.2003 (It cannot be VS 2005). The cheapest is
VB.Net
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"refdk" <fuhlendorf@.gmail.com> wrote in message
news:1140804364.362272.141300@.z34g2000cwc.googlegroups.com...
> What is the minimum requirement or version of Visual Studio.NET
> necessary for editing reports when running Reporting Services. I am
> running on a SQL 2000 sp3 and Windows 2003 server.
>|||Thanks, I will try that :-)
/Ren=E9

Minimum RAM Requirement For installation

256 RAM is running on my computer. is it possible to run Microsoft SQL Server 2005 Reporting Services on it?

NOTE: I installed Microsoft SQL Server 2005 Reporting Services. By the installation, it gives an error, that system resource is not enough. Although this, installation resume, but program not worked at the end.

I

No.

http://www.microsoft.com/downloads/details.aspx?familyid=1E53F882-0C16-4847-B331-132274AE8C84&displaylang=en#Requirements

minimum privileges

what are the minimum privileges required by the sql server id used by
reporting services to access it's data store (ReportingServices and
ReportingServicesTempDB)? The install gives the id specified in the install
dbo privilliges and our DBA is complaningThe minimum should be that the ID needs the right to login to report server
and it needs the RSExec role for the following:
ReportServer
ReportServerTempDB
MSDB
Master
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Richard" <Richard@.discussions.microsoft.com> wrote in message
news:7FE38CB6-0BD4-441A-8B1C-E06FCB89D103@.microsoft.com...
> what are the minimum privileges required by the sql server id used by
> reporting services to access it's data store (ReportingServices and
> ReportingServicesTempDB)? The install gives the id specified in the
> install
> dbo privilliges and our DBA is complaning

Minimum NTFS Permissions required for SQL Server Reporting Services to run

I posted elsewhere my troubles in installing SQL Server Reporting services
on my development server. This server is locked down in (almost) the exact
same way as our production server in order to prove the ability of
applications to run and to protect our software under development.
I used two documents from Microsoft to set the NTFS Permissions:
Minimum NTFS Permissions Required for IIS 5.0 To work:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q271071
and Aspnet_wp.exe Could Not Be Started Error Message When You View an
ASP.Net Page:
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B811320
I was not able to install SQL Server Reporting Services when the NTFS
permissions were set as documented. I was forced to make the ASPNet user an
administrator to install, this proves that the issue is permission related.
I have not been able to find a document outlining the permissions needed for
SQL Server Reporting Services. Is anyone aware of one? Our servers must be
as secure as is reasonably possible so I need this information.
Thank you.Hmm.Were you trying to install RS while logged in as ASPnet user? As is not
atypical, when installing a server application you need to be logged in as
someone with Administrator priveleges on the server. However, this does not
mean that the accounts that run need to be in the admin group. When I
install it I log in as log administrator and install it. There is no reason
for aspnet user to be adminstrator (it isn't in my configuration).
Bruce L-C
"Roger Twomey" <rogerdev@.vnet.on.ca> wrote in message
news:%237ydtdTWEHA.1048@.tk2msftngp13.phx.gbl...
> I posted elsewhere my troubles in installing SQL Server Reporting services
> on my development server. This server is locked down in (almost) the exact
> same way as our production server in order to prove the ability of
> applications to run and to protect our software under development.
> I used two documents from Microsoft to set the NTFS Permissions:
> Minimum NTFS Permissions Required for IIS 5.0 To work:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q271071
> and Aspnet_wp.exe Could Not Be Started Error Message When You View an
> ASP.Net Page:
> http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B811320
> I was not able to install SQL Server Reporting Services when the NTFS
> permissions were set as documented. I was forced to make the ASPNet user
an
> administrator to install, this proves that the issue is permission
related.
> I have not been able to find a document outlining the permissions needed
for
> SQL Server Reporting Services. Is anyone aware of one? Our servers must be
> as secure as is reasonably possible so I need this information.
> Thank you.
>

Minimum config to upgrade 2000 to 2005?

I am trying to upgrade from SQL Server 2000 Developer Edition (SP4) to SQL Server 2005 Developer Edition. I want to be able to use Reporting Services in the 2005 version. But the 2005 Upgrade Advisor says:

Reporting Services is either not installed or is installed incorrectly.
- Virtual directory settings do not match the default configuration
- Custom virtual directory settings block edition upgrades
- Custom extensions are deployed on the report server
- ASP.NET account information is encrypted

What do I need to install from the 2000 product in order to be able to upgrade to the 2005 version?

You should only get this warning if one of these conditions is true. Have you verfied each one?

Here is how to check:

1) Have you modified the IIS settings for either the Report or ReportServer vdir in any way?

2) Did you modify the config file to add any custom extensions?

3) Is your machine.config file set to encrypt the asp.net account password?

If you check all of this and still can't find the issue, you can always uninstall RS (this will still leave the RS catalog around), Install RS 2005. Use the 2005 configuration tool to point RS to the old DB and upgrade it to the new schema. The use that DB as the report server DB. You will then continue to maintain all of your old reports but will gain all the new features of RS 2005.

|||

Daniel, thanks for your help. I'm on the (very) low end of experience with all this.

>1) Have you modified the IIS settings for either the Report or ReportServer vdir in any way?

I uninstalled all SQL Server components (both 2005 and 2000) and then reinstalled 2000, 2000 SP4 and 2005. So, it seems like the answer here is no.

>2) Did you modify the config file to add any custom extensions?

I don't think so. Where should I look?

>3) Is your machine.config file set to encrypt the asp.net account password?

Where should I look for this file? (I guess the fact that I'm even asking this implies I have not messed with it ... but don't assume too much.)

>If you check all of this and still can't find the issue, you can always uninstall RS

I don't think it was ever installed in the first place.

|||It sounds like you are just trying to install RS2005. You do not need to install RS 2000 to get RS2005. Just install 2005.|||

Daniel Reib wrote:

If you check all of this and still can't find the issue, you can always uninstall RS (this will still leave the RS catalog around), Install RS 2005. Use the 2005 configuration tool to point RS to the old DB and upgrade it to the new schema. The use that DB as the report server DB. You will then continue to maintain all of your old reports but will gain all the new features of RS 2005.

I have a case where I need to upgrade both the DB and the RS from 2000 to 2005. The procedure above seem to work great except from one thing - I don't know how to transfer the encryption keys. I have made the keyfile with rskeymgmt but in the 2005 config screen i get an error when trying to restore the encryption keys:

ReportServicesConfigUI.WMIProvider.WMIProviderException: Could not find stored procedure 'SetKeysForInstallation'.
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.RestoreEncryptionKey(Byte[] encryptedBytes, String password)

Anyone knows what this means?

Regards,

|||This procedure was added for RS2005. It appears like you are still pointing to your RS 2000 db or it has not upgraded correctly.|||

Still pointing to the RS 2000 db, isn't that what you say we should do? And RS 2005 will upgrade the schema? That step reported no errors whatsoever..

|||When you point to the 2000 DB the config tool should tell you that it is upgrading. If it did not you can always script the upgrade (using the config tool) and then just run the scripts.|||

That step didn't report any errors, it worked out great. The only config step I still have problems with is Encryption Keys (which reports the error I posted earlier) and Initialization (reports an x in the icon, and I'm not able to click it. It's grayed out).

I tried the following now:

C:\Documents and Settings\Administrator>rskeymgmt -a -fdesktop\keys.snk -ppassword

Could not find stored procedure 'SetKeysForInstallation'.

C:\Documents and Settings\Administrator>

Which is basicly the same error as I posted earlier... any idea of what step I've missed that can cause this? I see that it's true.. there is no sp names SetKeysForInstallation in the db..

Minimum config to upgrade 2000 to 2005?

I am trying to upgrade from SQL Server 2000 Developer Edition (SP4) to SQL Server 2005 Developer Edition. I want to be able to use Reporting Services in the 2005 version. But the 2005 Upgrade Advisor says:

Reporting Services is either not installed or is installed incorrectly.
- Virtual directory settings do not match the default configuration
- Custom virtual directory settings block edition upgrades
- Custom extensions are deployed on the report server
- ASP.NET account information is encrypted

What do I need to install from the 2000 product in order to be able to upgrade to the 2005 version?

You should only get this warning if one of these conditions is true. Have you verfied each one?

Here is how to check:

1) Have you modified the IIS settings for either the Report or ReportServer vdir in any way?

2) Did you modify the config file to add any custom extensions?

3) Is your machine.config file set to encrypt the asp.net account password?

If you check all of this and still can't find the issue, you can always uninstall RS (this will still leave the RS catalog around), Install RS 2005. Use the 2005 configuration tool to point RS to the old DB and upgrade it to the new schema. The use that DB as the report server DB. You will then continue to maintain all of your old reports but will gain all the new features of RS 2005.

|||

Daniel, thanks for your help. I'm on the (very) low end of experience with all this.

>1) Have you modified the IIS settings for either the Report or ReportServer vdir in any way?

I uninstalled all SQL Server components (both 2005 and 2000) and then reinstalled 2000, 2000 SP4 and 2005. So, it seems like the answer here is no.

>2) Did you modify the config file to add any custom extensions?

I don't think so. Where should I look?

>3) Is your machine.config file set to encrypt the asp.net account password?

Where should I look for this file? (I guess the fact that I'm even asking this implies I have not messed with it ... but don't assume too much.)

>If you check all of this and still can't find the issue, you can always uninstall RS

I don't think it was ever installed in the first place.

|||It sounds like you are just trying to install RS2005. You do not need to install RS 2000 to get RS2005. Just install 2005.|||

Daniel Reib wrote:

If you check all of this and still can't find the issue, you can always uninstall RS (this will still leave the RS catalog around), Install RS 2005. Use the 2005 configuration tool to point RS to the old DB and upgrade it to the new schema. The use that DB as the report server DB. You will then continue to maintain all of your old reports but will gain all the new features of RS 2005.

I have a case where I need to upgrade both the DB and the RS from 2000 to 2005. The procedure above seem to work great except from one thing - I don't know how to transfer the encryption keys. I have made the keyfile with rskeymgmt but in the 2005 config screen i get an error when trying to restore the encryption keys:

ReportServicesConfigUI.WMIProvider.WMIProviderException: Could not find stored procedure 'SetKeysForInstallation'.
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.RestoreEncryptionKey(Byte[] encryptedBytes, String password)

Anyone knows what this means?

Regards,

|||This procedure was added for RS2005. It appears like you are still pointing to your RS 2000 db or it has not upgraded correctly.|||

Still pointing to the RS 2000 db, isn't that what you say we should do? And RS 2005 will upgrade the schema? That step reported no errors whatsoever..

|||When you point to the 2000 DB the config tool should tell you that it is upgrading. If it did not you can always script the upgrade (using the config tool) and then just run the scripts.|||

That step didn't report any errors, it worked out great. The only config step I still have problems with is Encryption Keys (which reports the error I posted earlier) and Initialization (reports an x in the icon, and I'm not able to click it. It's grayed out).

I tried the following now:

C:\Documents and Settings\Administrator>rskeymgmt -a -fdesktop\keys.snk -ppassword

Could not find stored procedure 'SetKeysForInstallation'.

C:\Documents and Settings\Administrator>

Which is basicly the same error as I posted earlier... any idea of what step I've missed that can cause this? I see that it's true.. there is no sp names SetKeysForInstallation in the db..

sql

Minimum AD Rights for LAN Based RS

I understand that one must have certain rights in their role as publisher in
reporting services.
Does anyone know the minimum rights needed to allow a developer to publish
reports? Must they have domain admin rights.
Win 2000 Server running SQL server 2000 and RS on a domain.
Thank you in advance.
P.S. I was hoping to not have to give full Administrator rights to publish
reports.
RichExcept for the fact that members of the local administrators group (note
that I say local) has admin rights to RS, there is no correlation between
the rights / groups someone is in as a member of the domain. Because the
domain adminstrator group is usually a member of the local administrators
group this looks the same. Note that you can definitely give rights to any
domain group you want or to individual users. RS operates based on the role
that the user or group has been given rights to. What I do is create a local
group and then to that group I add the domain groups and users that I want
to have rights. I do this just because it is such a pain to create and
manage a domain group but it can work either way. Here are the roles that
you can assign to a user/group:
Browser May view folders, reports and subscribe to
reports.
Content Manager May manage content in the Report Server. This
includes folders, reports and resources.
My Reports May publish reports and linked reports; manage
folders, reports and resources in a users My Reports folder.
Publisher May publish reports and linked reports to the
Report Server.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Rich" <rwatson@.brick.net> wrote in message
news:uR60h1MfFHA.3912@.tk2msftngp13.phx.gbl...
>I understand that one must have certain rights in their role as publisher
>in reporting services.
> Does anyone know the minimum rights needed to allow a developer to publish
> reports? Must they have domain admin rights.
> Win 2000 Server running SQL server 2000 and RS on a domain.
> Thank you in advance.
> P.S. I was hoping to not have to give full Administrator rights to publish
> reports.
> Rich
>sql

Minimal configuration of .NET Visual Studio

Hi
What is a minimal configuration of .NET Visual Studio to setup Reporting
Service?
Regards,
GennadiWhat is needed is the 2003 IDE shell.
Visual Basic.NET 2003 version should be enough.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Gena" <gretchkosiy@.hotmail.com> wrote in message
news:uJQ0PpkiEHA.3148@.TK2MSFTNGP10.phx.gbl...
> Hi
> What is a minimal configuration of .NET Visual Studio to setup Reporting
> Service?
> Regards,
> Gennadi
>|||Thanx
Is there any possibilities to run away from .NET VisualStudio to create
reports? I mean any GUI tools.
Thanx
Gennadi
"Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
news:uzSqmxkiEHA.1764@.TK2MSFTNGP10.phx.gbl...
> What is needed is the 2003 IDE shell.
> Visual Basic.NET 2003 version should be enough.
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Gena" <gretchkosiy@.hotmail.com> wrote in message
> news:uJQ0PpkiEHA.3148@.TK2MSFTNGP10.phx.gbl...
> > Hi
> >
> > What is a minimal configuration of .NET Visual Studio to setup Reporting
> > Service?
> >
> > Regards,
> > Gennadi
> >
> >
>|||Report Designer is implemented as VS component and would not work without
VS.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Gena" <gretchkosiy@.hotmail.com> wrote in message
news:%23mwUt5kiEHA.3664@.TK2MSFTNGP11.phx.gbl...
> Thanx
> Is there any possibilities to run away from .NET VisualStudio to create
> reports? I mean any GUI tools.
> Thanx
> Gennadi
> "Lev Semenets [MSFT]" <levs@.microsoft.com> wrote in message
> news:uzSqmxkiEHA.1764@.TK2MSFTNGP10.phx.gbl...
>> What is needed is the 2003 IDE shell.
>> Visual Basic.NET 2003 version should be enough.
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> "Gena" <gretchkosiy@.hotmail.com> wrote in message
>> news:uJQ0PpkiEHA.3148@.TK2MSFTNGP10.phx.gbl...
>> > Hi
>> >
>> > What is a minimal configuration of .NET Visual Studio to setup
>> > Reporting
>> > Service?
>> >
>> > Regards,
>> > Gennadi
>> >
>> >
>>
>

Mimic SQL Server Management Studio behavior inside RS Report

I want to know how to mimic the SSMS behavior inside an Reporting Services report when querying an XML field.

In SSMS, a field that is XML shows up as a link, and when the use clicks on the XML, it opens then entire XML document in a new window. I need this exact behavior in RS, but can't accomplish it.

Any smart people out there who can do this?

You would need to use a drillthrough or hyperlink action in the report. You could pass the value of the XML to the target URL.|||

Brian, thats the part that I dont understand. The target isn't in a file- it's in a field in the database. So, with one hyperlink action how do I extract the data, and present it in another IE window, formatted as XML (i.e. indentation, Expand/collapse nodes functionality, etc. like in IE or SSMS)

You say "pass the value of the XML". How do I construnct the hyperlink to do that? Just assign the field to the Drill to URL action? That seems to easy, but I'll give it a shot...

-Kory

|||

I didn't realize you were trying to get an interactive representation of the XML. You can't really accomplish what you want in a report as we don't deal with XML data hierarchically - the XML data extension will flatten it and the binding it into a textbox will simply display the string. (Native XML support is in the long term plans)

So, if you want an interactive view, I would create an ASPX page that took the XML data as a parameter and displayed the HTML then create a URL action to point to the page.

MIMEType warning

Getting warning in reporting services report:
The value of the MIMEType property for the image ?image1? is ', which
is not a valid MIMEType.
my image is a .GIF and source is set to External. It is my understanding
that the MIMEType is ignored when source is External. I have also tried
setting the MIMETYPE to ="image/gif".
Any ideas'
ThanksWhen accessing an external image over a network protocol (e.g. http://...),
the target webserver should respond with the image data and the content
mimetype. If the target webserver provides an incorrect mimetype, it would
result in this type of warning message.
For external images from a network share or local paths we will try to
determine the mimetype based on the file extension (by a registry lookup).
In the very unlikely case that this registry lookup fails, the mimetype
would be empty.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"pb" <pbrechlin@.hotmail.com> wrote in message
news:O33ItSriEHA.632@.TK2MSFTNGP12.phx.gbl...
> Getting warning in reporting services report:
> The value of the MIMEType property for the image ?image1? is ', which
> is not a valid MIMEType.
> my image is a .GIF and source is set to External. It is my understanding
> that the MIMEType is ignored when source is External. I have also tried
> setting the MIMETYPE to ="image/gif".
> Any ideas'
> Thanks|||What do I need to look at in order to correct this if the webserver is
not providing the correct info?
I just realized that this problem only happens when I run the report
within the development environment. When I deploy the report and run it
the correct image appears in the report.
Robert Bruckner [MSFT] wrote:
> When accessing an external image over a network protocol (e.g. http://...),
> the target webserver should respond with the image data and the content
> mimetype. If the target webserver provides an incorrect mimetype, it would
> result in this type of warning message.
> For external images from a network share or local paths we will try to
> determine the mimetype based on the file extension (by a registry lookup).
> In the very unlikely case that this registry lookup fails, the mimetype
> would be empty.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "pb" <pbrechlin@.hotmail.com> wrote in message
> news:O33ItSriEHA.632@.TK2MSFTNGP12.phx.gbl...
>>Getting warning in reporting services report:
>>The value of the MIMEType property for the image ?image1? is ', which
>>is not a valid MIMEType.
>>my image is a .GIF and source is set to External. It is my understanding
>>that the MIMEType is ignored when source is External. I have also tried
>>setting the MIMETYPE to ="image/gif".
>>Any ideas'
>>Thanks
>
>|||Is the development environment on the same machine as the report server? If
not, probably there is a proxy or firewall involved when running it in the
development environment and therefore the mime type does not come through
correctly.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"pb" <pbrechlin@.hotmail.com> wrote in message
news:%23Xh8GUEjEHA.3972@.tk2msftngp13.phx.gbl...
> What do I need to look at in order to correct this if the webserver is
> not providing the correct info?
> I just realized that this problem only happens when I run the report
> within the development environment. When I deploy the report and run it
> the correct image appears in the report.
> Robert Bruckner [MSFT] wrote:
> > When accessing an external image over a network protocol (e.g.
http://...),
> > the target webserver should respond with the image data and the content
> > mimetype. If the target webserver provides an incorrect mimetype, it
would
> > result in this type of warning message.
> > For external images from a network share or local paths we will try to
> > determine the mimetype based on the file extension (by a registry
lookup).
> > In the very unlikely case that this registry lookup fails, the mimetype
> > would be empty.
> >
> > --
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "pb" <pbrechlin@.hotmail.com> wrote in message
> > news:O33ItSriEHA.632@.TK2MSFTNGP12.phx.gbl...
> >
> >>Getting warning in reporting services report:
> >>
> >>The value of the MIMEType property for the image ?image1? is ', which
> >>is not a valid MIMEType.
> >>
> >>my image is a .GIF and source is set to External. It is my understanding
> >>that the MIMEType is ignored when source is External. I have also tried
> >>setting the MIMETYPE to ="image/gif".
> >>
> >>Any ideas'
> >>Thanks
> >
> >
> >|||I began to get this error right after I installed "Office 2003 Pro".
Do you use MS Office 2003?
"Robert Bruckner [MSFT]" wrote:
> Is the development environment on the same machine as the report server? If
> not, probably there is a proxy or firewall involved when running it in the
> development environment and therefore the mime type does not come through
> correctly.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "pb" <pbrechlin@.hotmail.com> wrote in message
> news:%23Xh8GUEjEHA.3972@.tk2msftngp13.phx.gbl...
> > What do I need to look at in order to correct this if the webserver is
> > not providing the correct info?
> >
> > I just realized that this problem only happens when I run the report
> > within the development environment. When I deploy the report and run it
> > the correct image appears in the report.
> >
> > Robert Bruckner [MSFT] wrote:
> > > When accessing an external image over a network protocol (e.g.
> http://...),
> > > the target webserver should respond with the image data and the content
> > > mimetype. If the target webserver provides an incorrect mimetype, it
> would
> > > result in this type of warning message.
> > > For external images from a network share or local paths we will try to
> > > determine the mimetype based on the file extension (by a registry
> lookup).
> > > In the very unlikely case that this registry lookup fails, the mimetype
> > > would be empty.
> > >
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "pb" <pbrechlin@.hotmail.com> wrote in message
> > > news:O33ItSriEHA.632@.TK2MSFTNGP12.phx.gbl...
> > >
> > >>Getting warning in reporting services report:
> > >>
> > >>The value of the MIMEType property for the image â'image1â' is â'â', which
> > >>is not a valid MIMEType.
> > >>
> > >>my image is a .GIF and source is set to External. It is my understanding
> > >>that the MIMEType is ignored when source is External. I have also tried
> > >>setting the MIMETYPE to ="image/gif".
> > >>
> > >>Any ideas'
> > >>Thanks
> > >
> > >
> > >
>
>

Migration path of Reporting Servcies 2000 to 2005

This may have been asked before but can some one comment on migration path
for moving reporting services 2000 created reports to 2005.
Many thanks.It is supposed to be transparent. I am counting on it being so.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"ah_la_ma" <ah_la_ma@.yahoo.com> wrote in message
news:O0TL8xcNFHA.3420@.tk2msftngp13.phx.gbl...
> This may have been asked before but can some one comment on migration path
> for moving reporting services 2000 created reports to 2005.
> Many thanks.
>|||The goal is it is completely transparent. RS 2005 supports both 2000 and
2005 report definitions. If you load a 2000 report into the 2005 report
designer, it will upgrade it. The server will also support both 2000 and
2005 web services clients.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"ah_la_ma" <ah_la_ma@.yahoo.com> wrote in message
news:O0TL8xcNFHA.3420@.tk2msftngp13.phx.gbl...
> This may have been asked before but can some one comment on migration path
> for moving reporting services 2000 created reports to 2005.
> Many thanks.
>

Migration of SQL 2000 Reporting Services

Hi,
I would like to migrate the SQL 2000 reporting services from one server to
another.
I tried to search for some articles or so, but didnt find much :(
Anyone have any idea from where i should start please or anyone knows of any
guide?hi Robert,
You can find ample information from this Knowledge base. Go to this link
http://support.microsoft.com/?kbid=842425
Regards
Sai Krishna
"Robert Abela" wrote:
> Hi,
> I would like to migrate the SQL 2000 reporting services from one server to
> another.
> I tried to search for some articles or so, but didnt find much :(
> Anyone have any idea from where i should start please or anyone knows of any
> guide?
>
>|||Hi Sai,
Thanks for the article.
I did the migration, and got a couple of errors, but error after error i am
arriving somewhere :)
Now i am stuck with this error and it seems i cannot go any further :(
Any idea?
This edition of Reporting Services does not support web farm deployment.
(rsInvalidRSEditionConfiguration)
"Sai Krishna" <SaiKrishna@.discussions.microsoft.com> wrote in message
news:AB775534-BCEA-4EF3-81C5-33A0BBF36238@.microsoft.com...
> hi Robert,
> You can find ample information from this Knowledge base. Go to this link
> http://support.microsoft.com/?kbid=842425
> Regards
> Sai Krishna
> "Robert Abela" wrote:
>> Hi,
>> I would like to migrate the SQL 2000 reporting services from one server
>> to
>> another.
>> I tried to search for some articles or so, but didnt find much :(
>> Anyone have any idea from where i should start please or anyone knows of
>> any
>> guide?
>>
>>|||Not sure what you are doing but I can tell you what this means. Web farm
deployment is when you have multiple RS servers all sharing the same
database for its metadata/object store. This means that your database is on
another server than RS and you are trying to have a second RS use it. Web
farms are only supported with Enterprise version.
If you are not trying to do this, it is what RS thinks you are trying to do.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Robert Abela" <abelarobert@.hotmail.com> wrote in message
news:ujcYQE7uGHA.4460@.TK2MSFTNGP05.phx.gbl...
> Hi Sai,
> Thanks for the article.
> I did the migration, and got a couple of errors, but error after error i
> am arriving somewhere :)
> Now i am stuck with this error and it seems i cannot go any further :(
> Any idea?
> This edition of Reporting Services does not support web farm deployment.
> (rsInvalidRSEditionConfiguration)
>
> "Sai Krishna" <SaiKrishna@.discussions.microsoft.com> wrote in message
> news:AB775534-BCEA-4EF3-81C5-33A0BBF36238@.microsoft.com...
>> hi Robert,
>> You can find ample information from this Knowledge base. Go to this
>> link
>> http://support.microsoft.com/?kbid=842425
>> Regards
>> Sai Krishna
>> "Robert Abela" wrote:
>> Hi,
>> I would like to migrate the SQL 2000 reporting services from one server
>> to
>> another.
>> I tried to search for some articles or so, but didnt find much :(
>> Anyone have any idea from where i should start please or anyone knows of
>> any
>> guide?
>>
>>
>

Migration from ComponentOne Reporting Service to SQL 2005 RS

Hi,
Is it possible to migrate from Component RS to SQL 2005 RS?Hi,
Is it possible to migrate from ComponentOne RS to SQL 2005 RS?

Migration form MS access reports to Sql server reports

Does any of the free dowloadable reporting packs come with Reporting Services wizard to migrate data and reports from MS-Access?

Does SQL Server reporting tools come integrated with any of the VS 2005 tools?

Yes, if you are dealing with the 2000 version than have your service packs up to date and you have to have Access 2003 for the option to show up in your designer. Once you have Access 2003 it will give you the option under "project" --> "import reports".

I believe in 2005 it is under the same location: "project" --> "import reports"

I hope this helps.

|||I need to convert from MS Access 97 to .NET 2005.
Is this possible with Reporting tool?|||It may be, but with what is built into Reporting Services you have to have Access 2003. This doesn't mean you couldn't open the Access 97 database with a 2003 version of Access.