RS2008 with SQL 2005 (different question)

Slightly different than the post before it.
If we have SQL 2005 and we don't want to upgrade to 2008 what options
do we have with regards to using RS2008? Can it be purchased
separately or something? Our reporting server is running 2005 great
but we want to benefit from the advances in RS2008 without having to
upgrade and pay a ton of money for it and take up a lot of time and
effort to upgrade everything, including the DB engine.
Thanksbased on the webcasts i have seen, I don't think RS 2008 will be available
separately.
"SQL Guy" <aymantg@.gmail.com> wrote in message
news:35ac9e28-4e09-4098-930f-9de83298236a@.w28g2000hsf.googlegroups.com...
> Slightly different than the post before it.
> If we have SQL 2005 and we don't want to upgrade to 2008 what options
> do we have with regards to using RS2008? Can it be purchased
> separately or something? Our reporting server is running 2005 great
> but we want to benefit from the advances in RS2008 without having to
> upgrade and pay a ton of money for it and take up a lot of time and
> effort to upgrade everything, including the DB engine.
> Thanks|||I don't have the definitive word on this but my guess (and I am counting on
it) will be that this will be the same as RS2005 and SQL 2000. With that
combination you could run RS 2005 and have it use SQL 2000 database for its
metadata/object caching. This was/is fully supported and I ran that way for
6 months. My guess is that RS 2008 will be similar, that it will allow SQL
2005 to be used for its metadata/object caching.
Now, as far as licensing. I am assuming no change in licensing. Today you
have to have a SQL 2005 license for whatever server is running RS. So if it
is a web farm and you have 5 web servers all using the same DB, then all 5
web servers have to have a SQL 2005 server license. If you run RS 2005 on
the same server as SQL 2000, you have to have a SQL 2005 license. You just
have the option not to upgrade the database but you still have to have a
license.
HTH,
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"SQL Guy" <aymantg@.gmail.com> wrote in message
news:35ac9e28-4e09-4098-930f-9de83298236a@.w28g2000hsf.googlegroups.com...
> Slightly different than the post before it.
> If we have SQL 2005 and we don't want to upgrade to 2008 what options
> do we have with regards to using RS2008? Can it be purchased
> separately or something? Our reporting server is running 2005 great
> but we want to benefit from the advances in RS2008 without having to
> upgrade and pay a ton of money for it and take up a lot of time and
> effort to upgrade everything, including the DB engine.
> Thanks

rs.CreateReport() with overwrite set to true doesn't really overwrite

Here's the situation... We have a report that has been deployed to
production a few weeks ago. Since then the report has changed slightly; two
parameters have changed--one parameter went from not being marked internal
to being marked internal and the other parameter's default value changed
(just a simple string change).
Now we want to programmatically deploy the updated report to production and
overwrite the existing report, including all parameters and parameter
properties. However, when we try this, the parameters, as shown through
Report Manger, have not changed. They're the same as the original
deployment. And, there is no error/exception thrown that might be causing
the problem.
Here's the code snippet:
System.Byte[] definition = null;
ReportingService2005.Warning[] warnings = null;
string name = (string)dr["Name"]; // Variable that holds the name
string file = (string)dr["FullName"]; // Variable that holds the file
System.IO.FileStream stream = System.IO.File.OpenRead(file);
definition = new System.Byte[stream.Length];
stream.Read(definition, 0, (int)stream.Length);
stream.Close();
warnings = rs.CreateReport(name, parent, true, definition, null);
Any help is greatly appreciated. Thanks!Hello Imttag,
This issue may occured by the session the reporting services holding. So I
suggest you reset your IIS after you create the report.
If this still occured, you may try to delete the report first and then
recreate the report again.
Hope this helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks for the info! However, the first idea didn't help. I ran my code to
call the CreateReport method to overwrite the report (and everything worked
fine with no errors). Then I close the browser and went back in (a
completely new session), and no changes. The report appeared to be the old
report, not the new report.
We thought about the second idea (that is, delete the old report and deploy
the new report in its place), but we have another issue with that approach.
The reports will have linked reports, and if we delete the report the linked
reports will not be linked anymore. We need to replace/overwrite the report
and keep the links in place for any linked reports.
Any help/suggestions on how to do this?
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:OJiRNQjgHHA.6068@.TK2MSFTNGHUB02.phx.gbl...
> Hello Imttag,
> This issue may occured by the session the reporting services holding. So I
> suggest you reset your IIS after you create the report.
> If this still occured, you may try to delete the report first and then
> recreate the report again.
> Hope this helps.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
rights.
>|||The issue with the default parameters not changing is considered a
feature. They favour server admins over developers. Given that an
admin might of changed the default values from those that were
originally deployed they are always preserved.
What you can do is set the default for the parameters separately after
you call SetReportDefinition to update your report. I use code similar
to that below to loop through the parameters of a report and change
the default values:
ReportParameter[] objReportParameters =objReportingServer.GetReportParameters(ReportNameGoesHere, null, true,
null, null);
foreach (ReportParameter objParameter in objReportParameters)
{
if (objParameter.Name == ParameterToChange)
objParameter.DefaultValues[0] = SomeDefaultValue;
}
Hope this helps,
Shane.
On Apr 18, 11:55 pm, "lmttag" <lmt...@.newsgroup.nospam> wrote:
> Here's the situation... We have a report that has been deployed to
> production a few weeks ago. Since then the report has changed slightly; two
> parameters have changed--one parameter went from not being marked internal
> to being marked internal and the other parameter's default value changed
> (just a simple string change).
> Now we want to programmatically deploy the updated report to production and
> overwrite the existing report, including all parameters and parameter
> properties. However, when we try this, the parameters, as shown through
> Report Manger, have not changed. They're the same as the original
> deployment. And, there is no error/exception thrown that might be causing
> the problem.
> Here's the code snippet:
> System.Byte[] definition = null;
> ReportingService2005.Warning[] warnings = null;
> string name = (string)dr["Name"]; // Variable that holds the name
> string file = (string)dr["FullName"]; // Variable that holds the file
> System.IO.FileStream stream = System.IO.File.OpenRead(file);
> definition = new System.Byte[stream.Length];
> stream.Read(definition, 0, (int)stream.Length);
> stream.Close();
> warnings = rs.CreateReport(name, parent, true, definition, null);
> Any help is greatly appreciated. Thanks!|||I forgot to mention that after you update the parameters you'll need
to call SetReportParameters to save the changes.
Regards,
Shane.
On Apr 19, 2:50 pm, shanejokeeffe <shanejokee...@.gmail.com> wrote:
> The issue with the default parameters not changing is considered a
> feature. They favour server admins over developers. Given that an
> admin might of changed the default values from those that were
> originally deployed they are always preserved.
> What you can do is set the default for the parameters separately after
> you call SetReportDefinition to update your report. I use code similar
> to that below to loop through the parameters of a report and change
> the default values:
> ReportParameter[] objReportParameters => objReportingServer.GetReportParameters(ReportNameGoesHere, null, true,
> null, null);
> foreach (ReportParameter objParameter in objReportParameters)
> {
> if (objParameter.Name == ParameterToChange)
> objParameter.DefaultValues[0] = SomeDefaultValue;
> }
> Hope this helps,
> Shane.
> On Apr 18, 11:55 pm, "lmttag" <lmt...@.newsgroup.nospam> wrote:
> > Here's the situation... We have a report that has been deployed to
> > production a few weeks ago. Since then the report has changed slightly; two
> > parameters have changed--one parameter went from not being marked internal
> > to being marked internal and the other parameter's default value changed
> > (just a simple string change).
> > Now we want to programmatically deploy the updated report to production and
> > overwrite the existing report, including all parameters and parameter
> > properties. However, when we try this, the parameters, as shown through
> > Report Manger, have not changed. They're the same as the original
> > deployment. And, there is no error/exception thrown that might be causing
> > the problem.
> > Here's the code snippet:
> > System.Byte[] definition = null;
> > ReportingService2005.Warning[] warnings = null;
> > string name = (string)dr["Name"]; // Variable that holds the name
> > string file = (string)dr["FullName"]; // Variable that holds the file
> > System.IO.FileStream stream = System.IO.File.OpenRead(file);
> > definition = new System.Byte[stream.Length];
> > stream.Read(definition, 0, (int)stream.Length);
> > stream.Close();
> > warnings = rs.CreateReport(name, parent, true, definition, null);
> > Any help is greatly appreciated. Thanks!|||Thanks for the info Shane!
I'll look into your suggestion. It sounds good.
"shanejokeeffe" <shanejokeeffe@.gmail.com> wrote in message
news:1176991806.345375.95070@.b75g2000hsg.googlegroups.com...
> I forgot to mention that after you update the parameters you'll need
> to call SetReportParameters to save the changes.
> Regards,
> Shane.
> On Apr 19, 2:50 pm, shanejokeeffe <shanejokee...@.gmail.com> wrote:
> > The issue with the default parameters not changing is considered a
> > feature. They favour server admins over developers. Given that an
> > admin might of changed the default values from those that were
> > originally deployed they are always preserved.
> >
> > What you can do is set the default for the parameters separately after
> > you call SetReportDefinition to update your report. I use code similar
> > to that below to loop through the parameters of a report and change
> > the default values:
> >
> > ReportParameter[] objReportParameters => > objReportingServer.GetReportParameters(ReportNameGoesHere, null, true,
> > null, null);
> >
> > foreach (ReportParameter objParameter in objReportParameters)
> > {
> > if (objParameter.Name == ParameterToChange)
> > objParameter.DefaultValues[0] = SomeDefaultValue;
> >
> > }
> >
> > Hope this helps,
> >
> > Shane.
> >
> > On Apr 18, 11:55 pm, "lmttag" <lmt...@.newsgroup.nospam> wrote:
> >
> > > Here's the situation... We have a report that has been deployed to
> > > production a few weeks ago. Since then the report has changed
slightly; two
> > > parameters have changed--one parameter went from not being marked
internal
> > > to being marked internal and the other parameter's default value
changed
> > > (just a simple string change).
> >
> > > Now we want to programmatically deploy the updated report to
production and
> > > overwrite the existing report, including all parameters and parameter
> > > properties. However, when we try this, the parameters, as shown
through
> > > Report Manger, have not changed. They're the same as the original
> > > deployment. And, there is no error/exception thrown that might be
causing
> > > the problem.
> >
> > > Here's the code snippet:
> >
> > > System.Byte[] definition = null;
> > > ReportingService2005.Warning[] warnings = null;
> >
> > > string name = (string)dr["Name"]; // Variable that holds the name
> > > string file = (string)dr["FullName"]; // Variable that holds the file
> >
> > > System.IO.FileStream stream = System.IO.File.OpenRead(file);
> > > definition = new System.Byte[stream.Length];
> > > stream.Read(definition, 0, (int)stream.Length);
> > > stream.Close();
> >
> > > warnings = rs.CreateReport(name, parent, true, definition, null);
> >
> > > Any help is greatly appreciated. Thanks!
>