Showing posts with label services. Show all posts
Showing posts with label services. Show all posts

Friday, March 23, 2012

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 Requirements to issue an XMLA Command to analysis services

What are the minimum requirements (in terms of referenced assemblies) I need in .NET programming to issue and xmla command to the analysis services?

What we want to do?

We want to create and SSDS .NET Stored Procedure which inserts a value in an SSAS Dimension Table and then in the same procedure issue an SSAS XMLA Process ADD Command.

It must be an SQL Procedure because auf external requirements

The Issue

IF we reference the Namespaces "Microsoft.AnalysisServices" and "Microsoft.AnalysisServices.XMLA" we receive errors

CREATE ASSEMBLY failed because method "add_CollectionChanging" on type "Microsoft.AnalysisServices.ModelComponentCollection" in external_access assembly "Microsoft.AnalysisServices" has a synchronized attribute. Explicit synchronization is not allowed in external_access assemblies.

We are only able to allow EXTERNAL_ACCESS on the SQL Server but no UNSAFE Assemplies.

Therefor the question - what is the minimum possibility to issue an XMLA Command?

- what is the SQL Agent Job Step Analysis Services Command using?

- Could XMLA Commandes be executed through an Analysis Services 9.0 OLEDB Connection (by OLEDB Command)?

- Without AMO?

Thankes for your Help

HANNES

Microsoft.AnalysisServices.AdomdClient is another option for sending XMLA commands, but it also does not support partially trusted callers so you'll get the same error. Any assembly that allows you to execute arbitrary XMLA commands should require special code access permissions (or simply be marked as unsafe) since XMLA commands can change data or reviel sensitive data and thus have the potential to be dangerous for untrusted code running under a trusted user account.

What you can do is write your own assembly which uses one of these other assemblies to send the XMLA command and mark it as supporting partially trusted callers. You'll need to be very careful if you do this and limit the capabilities of this new assembly so that it cannot be used in any harmful way (since code you don't completely trust can run it.) This means it should not execute arbitrary XMLA commands or connect to arbirtrary sources. You'll need to read up on code access security if you go this route - both to get it to work and make sure you don't introduce a security weekness into your system. If you accept any parameters into the methods, also be sure you protect against XMLA injection (like SQL injection but for XMLA). This solution can work, but use extreme caution since it affects the security of your system.

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

Wednesday, March 21, 2012

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

Monday, March 12, 2012

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
> > >
> > >
> > >
>
>

Friday, March 9, 2012

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?
>>
>>
>

Wednesday, March 7, 2012

Migration from sybase 8.0 to mssql server 2005

Hi all,

Here i had a task to migrate sybase 8.0 database to mssqlserver 2005 .how can i migrate this using INTEGRATED SERVICES (SSIS) or any other options. .Please try to provide some basical info because i am new to sybase versions.

Maybe these article will help:
http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/part2/c0661.mspx
http://www.microsoft.com/technet/itsolutions/migration/unix/sybsqlsv/default.mspx
http://www.microsoft.com/downloads/details.aspx?familyid=E7541305-891F-494A-B58B-2EED819C4411&displaylang=en
http://www.microsoft.com/sql/prodinfo/compare/sybase.mspx
http://www.devarticles.com/c/a/SQL-Server/Migrating-from-Sybase-to-SQL-Server/|||Basically that artical explaining migration from sybase|unix to sqlserver 2000 But not mssql server 2005 ,i gone through that article before but i did not find any help from that please can you make it clear.

Saturday, February 25, 2012

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.

Monday, February 20, 2012

Migrating to Report Services

Or rather, migrating to local reports using the Microsoft Report
Services.
We are in the process of planning the next generation of our software,
and among other things we are contemplating which reporting platform
we will use.
Until now we have been using Crystal Report, but it seems to be
getting more and more heavy to work with, plus it is a rather hefty
investment, well it can be.
First a little history:
- Our software will be running on anything from a stand-alone PC with
no connection to the surrounding world, to large-scale "enterprise"
networks with several dozens of clients. As a result our reporting
platform must be able to handle this.
Originally Crystal Report handled this very nicely, in that regard
that we simply installed the runtime libraries on each PC with our
software and a bunch of report files locally. This is model our
customers are used to.
Now I have decided to check out Reporting Services, but I have a bit
of a difficult time wrapping my mind around the concept. Some things
seem very nice and elegant, but others seem somewhat less so. For one
thing, the reports seem a little too simple and no where nearly as
powerful as Crystal Reports.
Now, our database is usually called the same regardless of the
customer, and of course, the layout of the database is always the same
(some customers may have a few custom tables, etc). But internally we
may have any number of databases that is named differently (customer
backups, test databases etc). So I need a way of being able to set the
database "on-the-fly".
What (I think) I need:
- A way of designing local reports and setting the data source at
runtime.
- I do not want to use the web server exclusively.
- Initially I want local reports, but the central reporting server can
be an option.
- I want to be able to mix tabular/matrix and chart reports.
- I want to be able to show group headers and footers, as well as page
headers and footers.
- I want to have full access to all tables in the database, and not
being restricted once I select on table, or entity.
Basically, I want to use the Reporting Service, but I don't want to
loose the freedom in data selection that Crystal Report gives me.According to your description, you need to use both SQL Server Reporting
Services and local report tool, which is bundled with VS2005/8 (VS2003 is
bundled with CrystalReport.NET as local report tool, while VS2005/8 come
with both CrystalReport.NET and MS report tool).
More comments inline.
"ThomasD" <tho.due@.gmail.com> wrote in message
news:4de6bed8-f6bc-4188-afd5-93ac01d49398@.8g2000hse.googlegroups.com...
> Or rather, migrating to local reports using the Microsoft Report
> Services.
> We are in the process of planning the next generation of our software,
> and among other things we are contemplating which reporting platform
> we will use.
> Until now we have been using Crystal Report, but it seems to be
> getting more and more heavy to work with, plus it is a rather hefty
> investment, well it can be.
> First a little history:
> - Our software will be running on anything from a stand-alone PC with
> no connection to the surrounding world, to large-scale "enterprise"
> networks with several dozens of clients. As a result our reporting
> platform must be able to handle this.
> Originally Crystal Report handled this very nicely, in that regard
> that we simply installed the runtime libraries on each PC with our
> software and a bunch of report files locally. This is model our
> customers are used to.
> Now I have decided to check out Reporting Services, but I have a bit
> of a difficult time wrapping my mind around the concept. Some things
> seem very nice and elegant, but others seem somewhat less so. For one
> thing, the reports seem a little too simple and no where nearly as
> powerful as Crystal Reports.
> Now, our database is usually called the same regardless of the
> customer, and of course, the layout of the database is always the same
> (some customers may have a few custom tables, etc). But internally we
> may have any number of databases that is named differently (customer
> backups, test databases etc). So I need a way of being able to set the
> database "on-the-fly".
> What (I think) I need:
> - A way of designing local reports and setting the data source at
> runtime.
If you have VS2005/8, you can do local report with either CrystalReport.NET
or MS report tool. By "Local". If you use SQL Server RS, I'd use MS report
tool in VS for local report, because the report viewer control can render
both local report and report from SQL Server RS. So, you app can seemlessly
dispaly report either from local report or from SQL Server RS without user
knowing the difference.
> - I do not want to use the web server exclusively.
> - Initially I want local reports, but the central reporting server can
> be an option.
> - I want to be able to mix tabular/matrix and chart reports.
> - I want to be able to show group headers and footers, as well as page
> headers and footers.
MS local report is a bit not as fancy as RS report can be.
> - I want to have full access to all tables in the database, and not
> being restricted once I select on table, or entity.
That has little to do with reporting, local or server.
> Basically, I want to use the Reporting Service, but I don't want to
> loose the freedom in data selection that Crystal Report gives me.
Do not know what "Data selection freedom" means here.
With local report, you can connect to whatever data source. If needed, you
can use code do trasform anything into a DataSet/Table of your desired
schema and use it as the report source, I'd think it is complete freedom.
With SQL Server RS, if the report data is difficult to access by reqular
queries, or the data source is not conventinal database, you can write your
own Data Processing Extensions sitting between the reporting processor and
data source. Of course, this requires lots of coding.|||> According to your description, you need to use both SQL Server Reporting
> Services and local report tool, which is bundled with VS2005/8 (VS2003 is
> bundled with CrystalReport.NET as local report tool, while VS2005/8 come
> with both CrystalReport.NET and MS report tool).
We use VS2008. I would like keep the option of using the report server
open, but my primary concern is local reports.
> More comments inline.
Cool. :)
> > - A way of designing local reports and setting the data source at
> > runtime.
> If you have VS2005/8, you can do local report with either CrystalReport.NET
> or MS report tool. By "Local". If you use SQL Server RS, I'd use MS report
> tool in VS for local report, because the report viewer control can render
> both local report and report from SQL Server RS. So, you app can seemlessly
> dispaly report either from local report or from SQL Server RS without user
> knowing the difference.
I finally managed to actually get the report designer working (it is
not easy to handle, when you are used to using Crystal Reports). It
looks very promising, however as it turns out, I have to supply the
data source "manually" when using the report locally. That is fine,
not a problem. However, I would like to use the SQL embedded in the
report, but that seems to be somewhat difficult to get at. So far I
have managed to get it by using XPath, but I can't help thinking that
there must be an easier way.
> MS local report is a bit not as fancy as RS report can be.
True, but I AM making progress in understanding the limitations and
differences.
> > - I want to have full access to all tables in the database, and not
> > being restricted once I select on table, or entity.
> That has little to do with reporting, local or server.
Well, after I "discovered" the report designer in Sql Server Business
Intelligence Development Studio (what a mouthful), I see that. Now I
just need to get a handle on the embedded SQL.
> > Basically, I want to use the Reporting Service, but I don't want to
> > loose the freedom in data selection that Crystal Report gives me.
> Do not know what "Data selection freedom" means here.
SQL. I don't want to be relying on some obscure model. Direct SQL
input is my preferred method of pulling data. Crystal Reports can do
both, and after discover the report designer in BI studio it looks
very promising.
> With local report, you can connect to whatever data source. If needed, you
> can use code do trasform anything into a DataSet/Table of your desired
> schema and use it as the report source, I'd think it is complete freedom.
> With SQL Server RS, if the report data is difficult to access by reqular
> queries, or the data source is not conventinal database, you can write your
> own Data Processing Extensions sitting between the reporting processor and
> data source. Of course, this requires lots of coding.
Coding doesn't scare me, I wouldn't be a software developer otherwise
*grin*
Regards,
Thomas