We have a SQL Server 2005 application that we deploy most of the time on SQL
Express, not full blown SQL. We have a Development box here (2 CPU XEON
with 4GB RAM) that has the Developer Edition and an instance of SQL Express
installed. If I run the same reports, with the same data, but one on the
developer edition and one on the Express Edition, there is a SIGNIFICANT
performance difference. This is a 1-page report - nothing huge, and it
renders in 2-3 seconds on Developer edition, but consistantly takes 15-20
seconds on the Express Edition.
I know SQL Express has a 1GB RAM limit, and a 1-CPU limit, but are there any
settings or anything that I can do to bring this closer to the full blown
SQL Version. This performance killing me onsite...
Any thoughts?
Thanks,
Markhave you identify if the problem is related to RS or SQL?
Does the SQL query is slower on the express edition? or the query takes the
same amount of time?
if the difference is here, then you have to play in the query and the
indexes to optimize it for the Express edition.
"Mark Essex" <messex@.netalytics.com> wrote in message
news:eyZTzG35HHA.980@.TK2MSFTNGP06.phx.gbl...
> We have a SQL Server 2005 application that we deploy most of the time on
> SQL Express, not full blown SQL. We have a Development box here (2 CPU
> XEON with 4GB RAM) that has the Developer Edition and an instance of SQL
> Express installed. If I run the same reports, with the same data, but one
> on the developer edition and one on the Express Edition, there is a
> SIGNIFICANT performance difference. This is a 1-page report - nothing
> huge, and it renders in 2-3 seconds on Developer edition, but consistantly
> takes 15-20 seconds on the Express Edition.
> I know SQL Express has a 1GB RAM limit, and a 1-CPU limit, but are there
> any settings or anything that I can do to bring this closer to the full
> blown SQL Version. This performance killing me onsite...
> Any thoughts?
> Thanks,
> Mark
>|||The query is 'instant' (less than a second) on both SQL Instances, so I
would say that this is an RS issue, not a SQL issue.
"Jeje" <willgart@.hotmail.com> wrote in message
news:2645D59B-223F-4F18-9712-AFF641F24C77@.microsoft.com...
> have you identify if the problem is related to RS or SQL?
> Does the SQL query is slower on the express edition? or the query takes
> the same amount of time?
> if the difference is here, then you have to play in the query and the
> indexes to optimize it for the Express edition.
>
> "Mark Essex" <messex@.netalytics.com> wrote in message
> news:eyZTzG35HHA.980@.TK2MSFTNGP06.phx.gbl...
>> We have a SQL Server 2005 application that we deploy most of the time on
>> SQL Express, not full blown SQL. We have a Development box here (2 CPU
>> XEON with 4GB RAM) that has the Developer Edition and an instance of SQL
>> Express installed. If I run the same reports, with the same data, but
>> one on the developer edition and one on the Express Edition, there is a
>> SIGNIFICANT performance difference. This is a 1-page report - nothing
>> huge, and it renders in 2-3 seconds on Developer edition, but
>> consistantly takes 15-20 seconds on the Express Edition.
>> I know SQL Express has a 1GB RAM limit, and a 1-CPU limit, but are there
>> any settings or anything that I can do to bring this closer to the full
>> blown SQL Version. This performance killing me onsite...
>> Any thoughts?
>> Thanks,
>> Mark
>>|||what is the connection string used by the report?
and does RS and SQL are on the same server?
"Mark Essex" <messex@.netalytics.com> wrote in message
news:eoyjDAJ6HHA.4880@.TK2MSFTNGP03.phx.gbl...
> The query is 'instant' (less than a second) on both SQL Instances, so I
> would say that this is an RS issue, not a SQL issue.
> "Jeje" <willgart@.hotmail.com> wrote in message
> news:2645D59B-223F-4F18-9712-AFF641F24C77@.microsoft.com...
>> have you identify if the problem is related to RS or SQL?
>> Does the SQL query is slower on the express edition? or the query takes
>> the same amount of time?
>> if the difference is here, then you have to play in the query and the
>> indexes to optimize it for the Express edition.
>>
>> "Mark Essex" <messex@.netalytics.com> wrote in message
>> news:eyZTzG35HHA.980@.TK2MSFTNGP06.phx.gbl...
>> We have a SQL Server 2005 application that we deploy most of the time on
>> SQL Express, not full blown SQL. We have a Development box here (2 CPU
>> XEON with 4GB RAM) that has the Developer Edition and an instance of SQL
>> Express installed. If I run the same reports, with the same data, but
>> one on the developer edition and one on the Express Edition, there is a
>> SIGNIFICANT performance difference. This is a 1-page report - nothing
>> huge, and it renders in 2-3 seconds on Developer edition, but
>> consistantly takes 15-20 seconds on the Express Edition.
>> I know SQL Express has a 1GB RAM limit, and a 1-CPU limit, but are there
>> any settings or anything that I can do to bring this closer to the full
>> blown SQL Version. This performance killing me onsite...
>> Any thoughts?
>> Thanks,
>> Mark
>>
>|||COnnection string looks like:
data source=.\installs; initial catalog = Methasoft53
RS and SQL are on the same machine.
Would the '.\installs' cause issues, meaning should I put the MACHINE NAME
in there, instead of using the 'dot' notation? Maybe a 'lookup' time issue?
Thanks,
Mark
"Jeje" <willgart@.hotmail.com> wrote in message
news:6C308FB1-6A82-440F-9746-8BED264C9313@.microsoft.com...
> what is the connection string used by the report?
> and does RS and SQL are on the same server?
> "Mark Essex" <messex@.netalytics.com> wrote in message
> news:eoyjDAJ6HHA.4880@.TK2MSFTNGP03.phx.gbl...
>> The query is 'instant' (less than a second) on both SQL Instances, so I
>> would say that this is an RS issue, not a SQL issue.
>> "Jeje" <willgart@.hotmail.com> wrote in message
>> news:2645D59B-223F-4F18-9712-AFF641F24C77@.microsoft.com...
>> have you identify if the problem is related to RS or SQL?
>> Does the SQL query is slower on the express edition? or the query takes
>> the same amount of time?
>> if the difference is here, then you have to play in the query and the
>> indexes to optimize it for the Express edition.
>>
>> "Mark Essex" <messex@.netalytics.com> wrote in message
>> news:eyZTzG35HHA.980@.TK2MSFTNGP06.phx.gbl...
>> We have a SQL Server 2005 application that we deploy most of the time
>> on SQL Express, not full blown SQL. We have a Development box here (2
>> CPU XEON with 4GB RAM) that has the Developer Edition and an instance
>> of SQL Express installed. If I run the same reports, with the same
>> data, but one on the developer edition and one on the Express Edition,
>> there is a SIGNIFICANT performance difference. This is a 1-page
>> report - nothing huge, and it renders in 2-3 seconds on Developer
>> edition, but consistantly takes 15-20 seconds on the Express Edition.
>> I know SQL Express has a 1GB RAM limit, and a 1-CPU limit, but are
>> there any settings or anything that I can do to bring this closer to
>> the full blown SQL Version. This performance killing me onsite...
>> Any thoughts?
>> Thanks,
>> Mark
>>
>>|||to see if there is a naming resolution issue, open the profiler on your
server, then run the report.
if you see the query 10 seconds after you click "view report", then there is
a name resolution issue. if you see the query in less then 1second, then
there is no naming issue and the problem is somewhere else.
but using the . (dot) should not cause name resolution issue.
but maybe there is an authentication issue.
try to use an SQL Server login instead of the windows authentication
data source=.\installs; initial catalog =Methasoft53;uid=<user>;pwd=<password>
"Mark Essex" <messex@.netalytics.com> wrote in message
news:Oqg98Rp6HHA.4584@.TK2MSFTNGP03.phx.gbl...
> COnnection string looks like:
> data source=.\installs; initial catalog = Methasoft53
> RS and SQL are on the same machine.
> Would the '.\installs' cause issues, meaning should I put the MACHINE NAME
> in there, instead of using the 'dot' notation? Maybe a 'lookup' time
> issue?
> Thanks,
> Mark
> "Jeje" <willgart@.hotmail.com> wrote in message
> news:6C308FB1-6A82-440F-9746-8BED264C9313@.microsoft.com...
>> what is the connection string used by the report?
>> and does RS and SQL are on the same server?
>> "Mark Essex" <messex@.netalytics.com> wrote in message
>> news:eoyjDAJ6HHA.4880@.TK2MSFTNGP03.phx.gbl...
>> The query is 'instant' (less than a second) on both SQL Instances, so I
>> would say that this is an RS issue, not a SQL issue.
>> "Jeje" <willgart@.hotmail.com> wrote in message
>> news:2645D59B-223F-4F18-9712-AFF641F24C77@.microsoft.com...
>> have you identify if the problem is related to RS or SQL?
>> Does the SQL query is slower on the express edition? or the query takes
>> the same amount of time?
>> if the difference is here, then you have to play in the query and the
>> indexes to optimize it for the Express edition.
>>
>> "Mark Essex" <messex@.netalytics.com> wrote in message
>> news:eyZTzG35HHA.980@.TK2MSFTNGP06.phx.gbl...
>> We have a SQL Server 2005 application that we deploy most of the time
>> on SQL Express, not full blown SQL. We have a Development box here (2
>> CPU XEON with 4GB RAM) that has the Developer Edition and an instance
>> of SQL Express installed. If I run the same reports, with the same
>> data, but one on the developer edition and one on the Express Edition,
>> there is a SIGNIFICANT performance difference. This is a 1-page
>> report - nothing huge, and it renders in 2-3 seconds on Developer
>> edition, but consistantly takes 15-20 seconds on the Express Edition.
>> I know SQL Express has a 1GB RAM limit, and a 1-CPU limit, but are
>> there any settings or anything that I can do to bring this closer to
>> the full blown SQL Version. This performance killing me onsite...
>> Any thoughts?
>> Thanks,
>> Mark
>>
>>
>
Showing posts with label edition. Show all posts
Showing posts with label edition. Show all posts
Tuesday, March 20, 2012
Reports over internet with Standard Edition Reporting Services
Hello,
I'm trying to view my reports over the internet.
I can browse to https://www.mysite.com/reports and it prompts me to log in
(integrated windows authentication) and I can view my list of reports.
When I click on a report I recieve a basic "The page cannot be displayed"
error.
I even tried just "basic" authentication within IIS but still get the same
error.
The server hosts both components (SQL Server & IIS) on a Windows 2003 SP1.
No special authentication, not a web farm, do I still need to get Enterprise
edition?
Help...
Thanks in advance,
GregCheck your IE address when you open your report, it must point to
http://yourserver/reports. It point to your internal RS, that's why you can
not open report from internet. It shows your list is because IIS is working.
still no clue?
check your config file. RSWebApplication.config under ReportManager
change
<ReportServerUrl>http://yourserver/reportserver</ReportServerUrl>
to
<ReportServerUrl>http://yourserver domain/reportserver</ReportServerUrl>
and then visit
http://your server domain/reports|||Thank you Wei Ming, this solved it for me.
"Wei Ming" wrote:
> Check your IE address when you open your report, it must point to
> http://yourserver/reports. It point to your internal RS, that's why you can
> not open report from internet. It shows your list is because IIS is working.
> still no clue?
> check your config file. RSWebApplication.config under ReportManager
> change
> <ReportServerUrl>http://yourserver/reportserver</ReportServerUrl>
> to
> <ReportServerUrl>http://yourserver domain/reportserver</ReportServerUrl>
> and then visit
> http://your server domain/reports
>|||Also, is there a way during setup that would resolve this?
"Wei Ming" wrote:
> Check your IE address when you open your report, it must point to
> http://yourserver/reports. It point to your internal RS, that's why you can
> not open report from internet. It shows your list is because IIS is working.
> still no clue?
> check your config file. RSWebApplication.config under ReportManager
> change
> <ReportServerUrl>http://yourserver/reportserver</ReportServerUrl>
> to
> <ReportServerUrl>http://yourserver domain/reportserver</ReportServerUrl>
> and then visit
> http://your server domain/reports
>|||I can not give u an answer for this, here is what I am thinking:
during setup, it will gather information from your computer, and save that
piece info into config file, if you can find that information ( for example,
hosts or registry ) and modify it. Your RS can be auto configured after
installation.
What's the peticular reason you like to config this during setup?|||For future deployments, instead of having a client go into a config file, I'd
rather have all of these settings done for them.
I'm curious, how did you find this answer?
"Wei Ming" wrote:
> I can not give u an answer for this, here is what I am thinking:
> during setup, it will gather information from your computer, and save that
> piece info into config file, if you can find that information ( for example,
> hosts or registry ) and modify it. Your RS can be auto configured after
> installation.
> What's the peticular reason you like to config this during setup?
I'm trying to view my reports over the internet.
I can browse to https://www.mysite.com/reports and it prompts me to log in
(integrated windows authentication) and I can view my list of reports.
When I click on a report I recieve a basic "The page cannot be displayed"
error.
I even tried just "basic" authentication within IIS but still get the same
error.
The server hosts both components (SQL Server & IIS) on a Windows 2003 SP1.
No special authentication, not a web farm, do I still need to get Enterprise
edition?
Help...
Thanks in advance,
GregCheck your IE address when you open your report, it must point to
http://yourserver/reports. It point to your internal RS, that's why you can
not open report from internet. It shows your list is because IIS is working.
still no clue?
check your config file. RSWebApplication.config under ReportManager
change
<ReportServerUrl>http://yourserver/reportserver</ReportServerUrl>
to
<ReportServerUrl>http://yourserver domain/reportserver</ReportServerUrl>
and then visit
http://your server domain/reports|||Thank you Wei Ming, this solved it for me.
"Wei Ming" wrote:
> Check your IE address when you open your report, it must point to
> http://yourserver/reports. It point to your internal RS, that's why you can
> not open report from internet. It shows your list is because IIS is working.
> still no clue?
> check your config file. RSWebApplication.config under ReportManager
> change
> <ReportServerUrl>http://yourserver/reportserver</ReportServerUrl>
> to
> <ReportServerUrl>http://yourserver domain/reportserver</ReportServerUrl>
> and then visit
> http://your server domain/reports
>|||Also, is there a way during setup that would resolve this?
"Wei Ming" wrote:
> Check your IE address when you open your report, it must point to
> http://yourserver/reports. It point to your internal RS, that's why you can
> not open report from internet. It shows your list is because IIS is working.
> still no clue?
> check your config file. RSWebApplication.config under ReportManager
> change
> <ReportServerUrl>http://yourserver/reportserver</ReportServerUrl>
> to
> <ReportServerUrl>http://yourserver domain/reportserver</ReportServerUrl>
> and then visit
> http://your server domain/reports
>|||I can not give u an answer for this, here is what I am thinking:
during setup, it will gather information from your computer, and save that
piece info into config file, if you can find that information ( for example,
hosts or registry ) and modify it. Your RS can be auto configured after
installation.
What's the peticular reason you like to config this during setup?|||For future deployments, instead of having a client go into a config file, I'd
rather have all of these settings done for them.
I'm curious, how did you find this answer?
"Wei Ming" wrote:
> I can not give u an answer for this, here is what I am thinking:
> during setup, it will gather information from your computer, and save that
> piece info into config file, if you can find that information ( for example,
> hosts or registry ) and modify it. Your RS can be auto configured after
> installation.
> What's the peticular reason you like to config this during setup?
Reports on Web farm-Please reply
Hi
We are planning to deploy SQL Server reports on our Internet site which is a
web farm of Windows 2003 web edition servers. We have total 9 boxes in our
Internet web farm and they sit in DMZ spread onto multiple locations. Our
dev/qa environment is inside our network and here are my questions:
1. Does the SQL Server database being used by our Internet servers has to be
in same DMZ domain or can it sit inside out network and then we can pass all
the db transactions back to database inside network? I read somewhere that RS
and SQL Server DB have to be on same domain to work. Is this correct?
2. Also I would like to know how we can deploy all the reports from our
internal dev/qa environment onto our Internet boxes on a continuous basis. I
guess I will have to setup report services on each box and then use some
scripting to move over the required files over to all 9 boxes. Is this
correct assumption? Do we need to copy some files onto each web servers or if
they are talking to same database then the moment we update the db, changes
will be reflected across all web farm sites? Is there any online resource
which describes this whole thing?
Please note that I am not SQL DBA and have just started using SQL Server
reports.
--
ThanksIf you are deploying over the internet then you need to use forms based
authentication and my understanding (but I am hazy on this so don't consider
the answer definitive) is the issue with domains will not matter.
I can answer your second question more definitively than the first. If you
look at a server and look for any rdl files you will not find any. When you
deploy you are not copying files. Deployment is the process where the
reports get stored in the object store for Reporting Services (i.e. in the
database). The whole point of a web farm is they all point to a single
database for the object store and they all see the same reports, report
cache, subscriptions, etc. As far as how you deploy, you can deploy from
your dev machines or you can copy the rdl files over someplace else and then
you scripting to deploy them. An example of how to do this ships with the
product (I always just deploy from the dev environment so I have no ever
scripted this but I know it is possible).
Note for a web farm you have to be running enterprise edition of SQL Server.
Also you need an enterprise edition license for each server in the web farm.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"tiwanap" <tiwanap@.discussions.microsoft.com> wrote in message
news:5A5A9C26-2106-4E25-9BC6-6E52000ED2CB@.microsoft.com...
> Hi
> We are planning to deploy SQL Server reports on our Internet site which is
> a
> web farm of Windows 2003 web edition servers. We have total 9 boxes in our
> Internet web farm and they sit in DMZ spread onto multiple locations. Our
> dev/qa environment is inside our network and here are my questions:
> 1. Does the SQL Server database being used by our Internet servers has to
> be
> in same DMZ domain or can it sit inside out network and then we can pass
> all
> the db transactions back to database inside network? I read somewhere that
> RS
> and SQL Server DB have to be on same domain to work. Is this correct?
> 2. Also I would like to know how we can deploy all the reports from our
> internal dev/qa environment onto our Internet boxes on a continuous basis.
> I
> guess I will have to setup report services on each box and then use some
> scripting to move over the required files over to all 9 boxes. Is this
> correct assumption? Do we need to copy some files onto each web servers or
> if
> they are talking to same database then the moment we update the db,
> changes
> will be reflected across all web farm sites? Is there any online resource
> which describes this whole thing?
> Please note that I am not SQL DBA and have just started using SQL Server
> reports.
> --
> Thanks
We are planning to deploy SQL Server reports on our Internet site which is a
web farm of Windows 2003 web edition servers. We have total 9 boxes in our
Internet web farm and they sit in DMZ spread onto multiple locations. Our
dev/qa environment is inside our network and here are my questions:
1. Does the SQL Server database being used by our Internet servers has to be
in same DMZ domain or can it sit inside out network and then we can pass all
the db transactions back to database inside network? I read somewhere that RS
and SQL Server DB have to be on same domain to work. Is this correct?
2. Also I would like to know how we can deploy all the reports from our
internal dev/qa environment onto our Internet boxes on a continuous basis. I
guess I will have to setup report services on each box and then use some
scripting to move over the required files over to all 9 boxes. Is this
correct assumption? Do we need to copy some files onto each web servers or if
they are talking to same database then the moment we update the db, changes
will be reflected across all web farm sites? Is there any online resource
which describes this whole thing?
Please note that I am not SQL DBA and have just started using SQL Server
reports.
--
ThanksIf you are deploying over the internet then you need to use forms based
authentication and my understanding (but I am hazy on this so don't consider
the answer definitive) is the issue with domains will not matter.
I can answer your second question more definitively than the first. If you
look at a server and look for any rdl files you will not find any. When you
deploy you are not copying files. Deployment is the process where the
reports get stored in the object store for Reporting Services (i.e. in the
database). The whole point of a web farm is they all point to a single
database for the object store and they all see the same reports, report
cache, subscriptions, etc. As far as how you deploy, you can deploy from
your dev machines or you can copy the rdl files over someplace else and then
you scripting to deploy them. An example of how to do this ships with the
product (I always just deploy from the dev environment so I have no ever
scripted this but I know it is possible).
Note for a web farm you have to be running enterprise edition of SQL Server.
Also you need an enterprise edition license for each server in the web farm.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"tiwanap" <tiwanap@.discussions.microsoft.com> wrote in message
news:5A5A9C26-2106-4E25-9BC6-6E52000ED2CB@.microsoft.com...
> Hi
> We are planning to deploy SQL Server reports on our Internet site which is
> a
> web farm of Windows 2003 web edition servers. We have total 9 boxes in our
> Internet web farm and they sit in DMZ spread onto multiple locations. Our
> dev/qa environment is inside our network and here are my questions:
> 1. Does the SQL Server database being used by our Internet servers has to
> be
> in same DMZ domain or can it sit inside out network and then we can pass
> all
> the db transactions back to database inside network? I read somewhere that
> RS
> and SQL Server DB have to be on same domain to work. Is this correct?
> 2. Also I would like to know how we can deploy all the reports from our
> internal dev/qa environment onto our Internet boxes on a continuous basis.
> I
> guess I will have to setup report services on each box and then use some
> scripting to move over the required files over to all 9 boxes. Is this
> correct assumption? Do we need to copy some files onto each web servers or
> if
> they are talking to same database then the moment we update the db,
> changes
> will be reflected across all web farm sites? Is there any online resource
> which describes this whole thing?
> Please note that I am not SQL DBA and have just started using SQL Server
> reports.
> --
> Thanks
Monday, March 12, 2012
Reports deployed to Standard edition RS and SQL Server
Hello,
We have successfully developed the reports on our testing machine with SQL Server 2000 Enterprise + Reporting Services 2000 Enterprise. Is there any problem if we deploy the reports to the production machine that runs SQL Server 2000 Standard and Reporting Services 2000 Standard?
We have successfully developed the reports on our testing machine with SQL Server 2000 Enterprise + Reporting Services 2000 Enterprise. Is there any problem if we deploy the reports to the production machine that runs SQL Server 2000 Standard and Reporting Services 2000 Standard?
Thanks in advance!
Here is some info on licensing:
http://msmvps.com/blogs/anguslogan/archive/2004/10/03/14788.aspx
The report RDL files should be the same in both environments so you should not have any problems.
cheers,
Andrew
Saturday, February 25, 2012
Reporting tools ?
Hi,
Is there a Reporting tools in SQL Server Standard Edition ? or it's actually
refering to the Analysis Services ?
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...-msde/200512/1
Reporting Services is a separate product which can be used if you have
a valid SQL Server 2k > licence, it not stuck to the analysis servces
but can keep benefit of this, due to the fact that you can use MDX
queries to access your database. The "tool set" to create Reporting
Services is brought to the dveloper by Visual Studio 2003 >.
HTH, Jens
|||Yes, SQL Server 2005 Reporting Services is included in Standard Edition
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:58e8077f9b87b@.uwe...
> Hi,
> Is there a Reporting tools in SQL Server Standard Edition ? or it's
> actually
> refering to the Analysis Services ?
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...-msde/200512/1
Is there a Reporting tools in SQL Server Standard Edition ? or it's actually
refering to the Analysis Services ?
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...-msde/200512/1
Reporting Services is a separate product which can be used if you have
a valid SQL Server 2k > licence, it not stuck to the analysis servces
but can keep benefit of this, due to the fact that you can use MDX
queries to access your database. The "tool set" to create Reporting
Services is brought to the dveloper by Visual Studio 2003 >.
HTH, Jens
|||Yes, SQL Server 2005 Reporting Services is included in Standard Edition
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:58e8077f9b87b@.uwe...
> Hi,
> Is there a Reporting tools in SQL Server Standard Edition ? or it's
> actually
> refering to the Analysis Services ?
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...-msde/200512/1
Reporting SVCS Installed?
I have DevStudio 2003, SQL Server 2000 (developer edition). I'd like to
switch from Crystal Reports 8.5 to MS Reporting Services. How can I upgrade
my SQL Server 2000 with this new reporting service/module? NOTE: I
purchased my SQL license in 2002.
There are no downloads in MSDN (except for an evaluation install), and no
options to upgrade to the latest version that includes the reprting service.
Also, where (on the Net) do I go to install the .Net components for
integration with the reporting service?There is a how to get RS info up on the RS website. Normally, it depends on
how you bought SQL Server. Most likely, you'll need to call your reseller
and get the RS CD from them.
Tom
"Billg_sd" <Billgsd@.discussions.microsoft.com> wrote in message
news:85432424-5394-42BE-BC39-3071F0C951EB@.microsoft.com...
>I have DevStudio 2003, SQL Server 2000 (developer edition). I'd like to
> switch from Crystal Reports 8.5 to MS Reporting Services. How can I
> upgrade
> my SQL Server 2000 with this new reporting service/module? NOTE: I
> purchased my SQL license in 2002.
> There are no downloads in MSDN (except for an evaluation install), and no
> options to upgrade to the latest version that includes the reprting
> service.
> Also, where (on the Net) do I go to install the .Net components for
> integration with the reporting service?
>
switch from Crystal Reports 8.5 to MS Reporting Services. How can I upgrade
my SQL Server 2000 with this new reporting service/module? NOTE: I
purchased my SQL license in 2002.
There are no downloads in MSDN (except for an evaluation install), and no
options to upgrade to the latest version that includes the reprting service.
Also, where (on the Net) do I go to install the .Net components for
integration with the reporting service?There is a how to get RS info up on the RS website. Normally, it depends on
how you bought SQL Server. Most likely, you'll need to call your reseller
and get the RS CD from them.
Tom
"Billg_sd" <Billgsd@.discussions.microsoft.com> wrote in message
news:85432424-5394-42BE-BC39-3071F0C951EB@.microsoft.com...
>I have DevStudio 2003, SQL Server 2000 (developer edition). I'd like to
> switch from Crystal Reports 8.5 to MS Reporting Services. How can I
> upgrade
> my SQL Server 2000 with this new reporting service/module? NOTE: I
> purchased my SQL license in 2002.
> There are no downloads in MSDN (except for an evaluation install), and no
> options to upgrade to the latest version that includes the reprting
> service.
> Also, where (on the Net) do I go to install the .Net components for
> integration with the reporting service?
>
Subscribe to:
Posts (Atom)