Hello folks,
I am currently working on a project plan to move from SQL7/NT4 to
SQL2005/Win2003 and I am putting together a documentation for our developers
regarding new features and deprecated features in 2005.
Can you point me to a detailed ducumentation on the programming side?
Thanks a lot.http://msdn2.microsoft.com/en-us/library/ms143729(en-US,SQL.90).aspx
and
http://msdn2.microsoft.com/en-us/library/ms144262.aspx
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Ata John" <AtaJohn@.discussions.microsoft.com> wrote in message
news:67622D5C-D5C8-4F16-89FA-2CDFD6730F01@.microsoft.com...
> Hello folks,
> I am currently working on a project plan to move from SQL7/NT4 to
> SQL2005/Win2003 and I am putting together a documentation for our
> developers
> regarding new features and deprecated features in 2005.
> Can you point me to a detailed ducumentation on the programming side?
> Thanks a lot.|||On Tue, 23 May 2006 22:22:23 +0100, "Tony Rogerson"
<tonyrogerson@.sqlserverfaq.com> wrote:
>http://msdn2.microsoft.com/en-us/library/ms143729(en-US,SQL.90).aspx
>and
>http://msdn2.microsoft.com/en-us/library/ms144262.aspx
One level up the tree from those:
http://msdn2.microsoft.com/en-us/library/ms143532.aspx
there are two more important links:
"Database Engine feature changes that might require changes to
applications."
http://msdn2.microsoft.com/en-us/library/ms143179.aspx
"Other changes in behavior to database features in this release."
http://msdn2.microsoft.com/en-us/library/ms143359.aspx
Roy Harvey
Beacon Falls, CTsql
Showing posts with label documentation. Show all posts
Showing posts with label documentation. Show all posts
Sunday, March 25, 2012
Deployment with Hardware Load balancing.
I am currently planning the deployment of reporting services into a hardware
load balanced environment. The documentation from MS only covers MS's NLB
software. Has anyone had any experience deploying with a hardware load
balancer. Specifically F5 load balencing equipment.
Thanks,
Adrian.Hello Adrian,
A report server Web farm is a collection of report server instances that
share the same report server database. Reporting Services does not provide
Web farm deployment functionality. To deploy Reporting Services in a Web
farm, you can use network load balancing (NLB) functionality provided
through Windows servers, Microsoft Application Center, or third-party
software that supports Web farm deployment. The load balancer can be
software or hardware.
For the "Steps for Deploying a Report Server Web Farm", please refer to the
"Steps for Deploying a Report Server Web Farm" section in the following web
site:
Enterprise Deployment Model
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm
/drp_deploying_v1_0h9e.asp
More information for reference:
Installing a Report Server Web Farm
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
tm/gs_installingrs_v1_2ckm.asp
305064 How To Set Up an NLB Cluster for Application Center 2000
http://support.microsoft.com/?id=305064
Regarding the information of how to implement and maintain NLB clusters, if
you use a third-party hardware load balancer, please contact the hardware
vendor support to inquire about this issue. I believe that they will assist
you best since they will have the proper material resources to resolve this
problem.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================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.|||Hi Sophie,
To confirm that I understand what you are saying, here is my take on how you
would deploy a multi node reporting server with hardware load balancing.
Note: Database tier is being deployed as active/active SQL Cluster.
1. Deploy the initial reporting services server node as per a vanilla
install.
2. Deploy any subsequent nodes by joining the nodes to the initial reporting
services node by specifying the RSWEBFARMSERVER property in the installation
3. Overlay the web nodes with either a hardware or software load balancing
solution.
Thanks,
Adrian.
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:Tu9WDs$QFHA.3704@.TK2MSFTNGXA02.phx.gbl...
> Hello Adrian,
> A report server Web farm is a collection of report server instances that
> share the same report server database. Reporting Services does not provide
> Web farm deployment functionality. To deploy Reporting Services in a Web
> farm, you can use network load balancing (NLB) functionality provided
> through Windows servers, Microsoft Application Center, or third-party
> software that supports Web farm deployment. The load balancer can be
> software or hardware.
> For the "Steps for Deploying a Report Server Web Farm", please refer to
> the
> "Steps for Deploying a Report Server Web Farm" section in the following
> web
> site:
> Enterprise Deployment Model
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm
> /drp_deploying_v1_0h9e.asp
> More information for reference:
> Installing a Report Server Web Farm
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
> tm/gs_installingrs_v1_2ckm.asp
> 305064 How To Set Up an NLB Cluster for Application Center 2000
> http://support.microsoft.com/?id=305064
> Regarding the information of how to implement and maintain NLB clusters,
> if
> you use a third-party hardware load balancer, please contact the hardware
> vendor support to inquire about this issue. I believe that they will
> assist
> you best since they will have the proper material resources to resolve
> this
> problem.
> I hope the information is helpful.
>
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> 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.
>|||One further point, this is an Enterprise only feature.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Adrian Russell" <adrianru@.avanade.com> wrote in message
news:ujF3s%23ARFHA.356@.TK2MSFTNGP14.phx.gbl...
> Hi Sophie,
> To confirm that I understand what you are saying, here is my take on how
you
> would deploy a multi node reporting server with hardware load balancing.
> Note: Database tier is being deployed as active/active SQL Cluster.
> 1. Deploy the initial reporting services server node as per a vanilla
> install.
> 2. Deploy any subsequent nodes by joining the nodes to the initial
reporting
> services node by specifying the RSWEBFARMSERVER property in the
installation
> 3. Overlay the web nodes with either a hardware or software load balancing
> solution.
> Thanks,
> Adrian.
> "Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
> news:Tu9WDs$QFHA.3704@.TK2MSFTNGXA02.phx.gbl...
> > Hello Adrian,
> >
> > A report server Web farm is a collection of report server instances that
> > share the same report server database. Reporting Services does not
provide
> > Web farm deployment functionality. To deploy Reporting Services in a Web
> > farm, you can use network load balancing (NLB) functionality provided
> > through Windows servers, Microsoft Application Center, or third-party
> > software that supports Web farm deployment. The load balancer can be
> > software or hardware.
> >
> > For the "Steps for Deploying a Report Server Web Farm", please refer to
> > the
> > "Steps for Deploying a Report Server Web Farm" section in the following
> > web
> > site:
> >
> > Enterprise Deployment Model
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm
> > /drp_deploying_v1_0h9e.asp
> >
> > More information for reference:
> >
> > Installing a Report Server Web Farm
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
> > tm/gs_installingrs_v1_2ckm.asp
> >
> > 305064 How To Set Up an NLB Cluster for Application Center 2000
> > http://support.microsoft.com/?id=305064
> >
> > Regarding the information of how to implement and maintain NLB clusters,
> > if
> > you use a third-party hardware load balancer, please contact the
hardware
> > vendor support to inquire about this issue. I believe that they will
> > assist
> > you best since they will have the proper material resources to resolve
> > this
> > problem.
> >
> > I hope the information is helpful.
> >
> >
> > Sophie Guo
> > Microsoft Online Partner Support
> >
> > Get Secure! - www.microsoft.com/security
> >
> > =====================================================> > 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.
> >
>|||By Enterprise only I mean both SQL Server db has to be enterprise and the
Reporting Services install has to be Enterprise. Plus, for each server in
the web farm with Reporting Services you need an SQL Server Enterprise
license.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Adrian Russell" <adrianru@.avanade.com> wrote in message
news:ujF3s%23ARFHA.356@.TK2MSFTNGP14.phx.gbl...
> Hi Sophie,
> To confirm that I understand what you are saying, here is my take on how
you
> would deploy a multi node reporting server with hardware load balancing.
> Note: Database tier is being deployed as active/active SQL Cluster.
> 1. Deploy the initial reporting services server node as per a vanilla
> install.
> 2. Deploy any subsequent nodes by joining the nodes to the initial
reporting
> services node by specifying the RSWEBFARMSERVER property in the
installation
> 3. Overlay the web nodes with either a hardware or software load balancing
> solution.
> Thanks,
> Adrian.
> "Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
> news:Tu9WDs$QFHA.3704@.TK2MSFTNGXA02.phx.gbl...
> > Hello Adrian,
> >
> > A report server Web farm is a collection of report server instances that
> > share the same report server database. Reporting Services does not
provide
> > Web farm deployment functionality. To deploy Reporting Services in a Web
> > farm, you can use network load balancing (NLB) functionality provided
> > through Windows servers, Microsoft Application Center, or third-party
> > software that supports Web farm deployment. The load balancer can be
> > software or hardware.
> >
> > For the "Steps for Deploying a Report Server Web Farm", please refer to
> > the
> > "Steps for Deploying a Report Server Web Farm" section in the following
> > web
> > site:
> >
> > Enterprise Deployment Model
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm
> > /drp_deploying_v1_0h9e.asp
> >
> > More information for reference:
> >
> > Installing a Report Server Web Farm
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
> > tm/gs_installingrs_v1_2ckm.asp
> >
> > 305064 How To Set Up an NLB Cluster for Application Center 2000
> > http://support.microsoft.com/?id=305064
> >
> > Regarding the information of how to implement and maintain NLB clusters,
> > if
> > you use a third-party hardware load balancer, please contact the
hardware
> > vendor support to inquire about this issue. I believe that they will
> > assist
> > you best since they will have the proper material resources to resolve
> > this
> > problem.
> >
> > I hope the information is helpful.
> >
> >
> > Sophie Guo
> > Microsoft Online Partner Support
> >
> > Get Secure! - www.microsoft.com/security
> >
> > =====================================================> > 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.
> >
>|||I'm operating in exactly this configuration. As mentioned by others,
its really straight forward to setup:
Prerequsites:
- A Sql Server 2000 Enterprise instance with SP3a
Installation:
1) Install Sql Reporting 2000 Enterprise on the first web server.
During installation it creates the needed ReportServer and
ReportServerTempDb databases.
2) Install Sql Reporting 2000 Enterprise on each subsequent server in
Farm and point them at the ReportServer DB created in step 1. (repeat
for each additional server)
3) Deploy RDL's via ReportsServer web service from any of the servers
(since they share the same DB and therefore will share the RDL's once
they are uploaded).
4) Start using your servers. (or begin applying Service packs)
Note: SP2 will require one extra step which is to run RSActivate in
order to join your additional Report Server nodes to the group. In
pre-SP2 installations, this is done automatically for you.
One thing to consider when doing the F5 setup; make sure to setup
Server Affinity using a time-based session so you don't run into any
problems with ASP.NET post-backs. Typically I set the session
expiration to 40 minutes, but it all depends upon your
user-characteristics. Also I have found it helpful to utilize the
"Least Used" algorithm rather than the default "Round Robin" approach
to load balancing.
Obviously, there are numerous architectural and infrastructural
decisions required throughout this process, but this should give you
the 10k meter view.
I am happy with F5 for load balancing so far, so I hope this works out
for you.
Enjoy.
Lance Hunt
http://weblogs.asp.net/lhunt/|||Hello Adrian,
For the second item:
2. Deploy any subsequent nodes by joining the nodes to the initial
reporting services node by specifying the RSWEBFARMSERVER property in the
installation
The RSWEBFARMSERVER property is specified in the command prompt. To install
a web farm, you have to specify the RSDATABASENAME and RSDATABASESERVER
property in the command prompt.
For more information, please refer to the following topic in BOL:
"Installing Reporting Services From the Command Line"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
tm/gs_installingrs_v1_6h6h.asp
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================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.|||Hi!
I'm also F5 Hardware load balancing, but I'm running into a problem.
Right now, we have 2 web servers in a cluster, and an F5 load balancer
infront of it. Both web servers have Kerberos delegation enabled, and
I can access Reporting services via Web Service just fine when I access
the web servers directly. However, when I put the F5 load balancer
infront, I get an Authentication error. The load balancer appears to
be sending my credentials as Anonymous! Has this happened to anyone?
Is there a Kerberos setting on this F5 hardware load balancer? I'm
unfamiliar with the hardware, and I'm trying to contact my IT
department to contact the vendor. That might take a while. I'm hoping
someone here has an answer.
Thanks!
Roy Assaly
Sophie Guo [MSFT] wrote:
> Hello Adrian,
> For the second item:
> 2. Deploy any subsequent nodes by joining the nodes to the initial
> reporting services node by specifying the RSWEBFARMSERVER property in
the
> installation
> The RSWEBFARMSERVER property is specified in the command prompt. To
install
> a web farm, you have to specify the RSDATABASENAME and
RSDATABASESERVER
> property in the command prompt.
> For more information, please refer to the following topic in BOL:
> "Installing Reporting Services From the Command Line"
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
> tm/gs_installingrs_v1_6h6h.asp
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> 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.
load balanced environment. The documentation from MS only covers MS's NLB
software. Has anyone had any experience deploying with a hardware load
balancer. Specifically F5 load balencing equipment.
Thanks,
Adrian.Hello Adrian,
A report server Web farm is a collection of report server instances that
share the same report server database. Reporting Services does not provide
Web farm deployment functionality. To deploy Reporting Services in a Web
farm, you can use network load balancing (NLB) functionality provided
through Windows servers, Microsoft Application Center, or third-party
software that supports Web farm deployment. The load balancer can be
software or hardware.
For the "Steps for Deploying a Report Server Web Farm", please refer to the
"Steps for Deploying a Report Server Web Farm" section in the following web
site:
Enterprise Deployment Model
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm
/drp_deploying_v1_0h9e.asp
More information for reference:
Installing a Report Server Web Farm
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
tm/gs_installingrs_v1_2ckm.asp
305064 How To Set Up an NLB Cluster for Application Center 2000
http://support.microsoft.com/?id=305064
Regarding the information of how to implement and maintain NLB clusters, if
you use a third-party hardware load balancer, please contact the hardware
vendor support to inquire about this issue. I believe that they will assist
you best since they will have the proper material resources to resolve this
problem.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================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.|||Hi Sophie,
To confirm that I understand what you are saying, here is my take on how you
would deploy a multi node reporting server with hardware load balancing.
Note: Database tier is being deployed as active/active SQL Cluster.
1. Deploy the initial reporting services server node as per a vanilla
install.
2. Deploy any subsequent nodes by joining the nodes to the initial reporting
services node by specifying the RSWEBFARMSERVER property in the installation
3. Overlay the web nodes with either a hardware or software load balancing
solution.
Thanks,
Adrian.
"Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
news:Tu9WDs$QFHA.3704@.TK2MSFTNGXA02.phx.gbl...
> Hello Adrian,
> A report server Web farm is a collection of report server instances that
> share the same report server database. Reporting Services does not provide
> Web farm deployment functionality. To deploy Reporting Services in a Web
> farm, you can use network load balancing (NLB) functionality provided
> through Windows servers, Microsoft Application Center, or third-party
> software that supports Web farm deployment. The load balancer can be
> software or hardware.
> For the "Steps for Deploying a Report Server Web Farm", please refer to
> the
> "Steps for Deploying a Report Server Web Farm" section in the following
> web
> site:
> Enterprise Deployment Model
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm
> /drp_deploying_v1_0h9e.asp
> More information for reference:
> Installing a Report Server Web Farm
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
> tm/gs_installingrs_v1_2ckm.asp
> 305064 How To Set Up an NLB Cluster for Application Center 2000
> http://support.microsoft.com/?id=305064
> Regarding the information of how to implement and maintain NLB clusters,
> if
> you use a third-party hardware load balancer, please contact the hardware
> vendor support to inquire about this issue. I believe that they will
> assist
> you best since they will have the proper material resources to resolve
> this
> problem.
> I hope the information is helpful.
>
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> 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.
>|||One further point, this is an Enterprise only feature.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Adrian Russell" <adrianru@.avanade.com> wrote in message
news:ujF3s%23ARFHA.356@.TK2MSFTNGP14.phx.gbl...
> Hi Sophie,
> To confirm that I understand what you are saying, here is my take on how
you
> would deploy a multi node reporting server with hardware load balancing.
> Note: Database tier is being deployed as active/active SQL Cluster.
> 1. Deploy the initial reporting services server node as per a vanilla
> install.
> 2. Deploy any subsequent nodes by joining the nodes to the initial
reporting
> services node by specifying the RSWEBFARMSERVER property in the
installation
> 3. Overlay the web nodes with either a hardware or software load balancing
> solution.
> Thanks,
> Adrian.
> "Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
> news:Tu9WDs$QFHA.3704@.TK2MSFTNGXA02.phx.gbl...
> > Hello Adrian,
> >
> > A report server Web farm is a collection of report server instances that
> > share the same report server database. Reporting Services does not
provide
> > Web farm deployment functionality. To deploy Reporting Services in a Web
> > farm, you can use network load balancing (NLB) functionality provided
> > through Windows servers, Microsoft Application Center, or third-party
> > software that supports Web farm deployment. The load balancer can be
> > software or hardware.
> >
> > For the "Steps for Deploying a Report Server Web Farm", please refer to
> > the
> > "Steps for Deploying a Report Server Web Farm" section in the following
> > web
> > site:
> >
> > Enterprise Deployment Model
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm
> > /drp_deploying_v1_0h9e.asp
> >
> > More information for reference:
> >
> > Installing a Report Server Web Farm
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
> > tm/gs_installingrs_v1_2ckm.asp
> >
> > 305064 How To Set Up an NLB Cluster for Application Center 2000
> > http://support.microsoft.com/?id=305064
> >
> > Regarding the information of how to implement and maintain NLB clusters,
> > if
> > you use a third-party hardware load balancer, please contact the
hardware
> > vendor support to inquire about this issue. I believe that they will
> > assist
> > you best since they will have the proper material resources to resolve
> > this
> > problem.
> >
> > I hope the information is helpful.
> >
> >
> > Sophie Guo
> > Microsoft Online Partner Support
> >
> > Get Secure! - www.microsoft.com/security
> >
> > =====================================================> > 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.
> >
>|||By Enterprise only I mean both SQL Server db has to be enterprise and the
Reporting Services install has to be Enterprise. Plus, for each server in
the web farm with Reporting Services you need an SQL Server Enterprise
license.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Adrian Russell" <adrianru@.avanade.com> wrote in message
news:ujF3s%23ARFHA.356@.TK2MSFTNGP14.phx.gbl...
> Hi Sophie,
> To confirm that I understand what you are saying, here is my take on how
you
> would deploy a multi node reporting server with hardware load balancing.
> Note: Database tier is being deployed as active/active SQL Cluster.
> 1. Deploy the initial reporting services server node as per a vanilla
> install.
> 2. Deploy any subsequent nodes by joining the nodes to the initial
reporting
> services node by specifying the RSWEBFARMSERVER property in the
installation
> 3. Overlay the web nodes with either a hardware or software load balancing
> solution.
> Thanks,
> Adrian.
> "Sophie Guo [MSFT]" <v-sguo@.online.microsoft.com> wrote in message
> news:Tu9WDs$QFHA.3704@.TK2MSFTNGXA02.phx.gbl...
> > Hello Adrian,
> >
> > A report server Web farm is a collection of report server instances that
> > share the same report server database. Reporting Services does not
provide
> > Web farm deployment functionality. To deploy Reporting Services in a Web
> > farm, you can use network load balancing (NLB) functionality provided
> > through Windows servers, Microsoft Application Center, or third-party
> > software that supports Web farm deployment. The load balancer can be
> > software or hardware.
> >
> > For the "Steps for Deploying a Report Server Web Farm", please refer to
> > the
> > "Steps for Deploying a Report Server Web Farm" section in the following
> > web
> > site:
> >
> > Enterprise Deployment Model
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm
> > /drp_deploying_v1_0h9e.asp
> >
> > More information for reference:
> >
> > Installing a Report Server Web Farm
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
> > tm/gs_installingrs_v1_2ckm.asp
> >
> > 305064 How To Set Up an NLB Cluster for Application Center 2000
> > http://support.microsoft.com/?id=305064
> >
> > Regarding the information of how to implement and maintain NLB clusters,
> > if
> > you use a third-party hardware load balancer, please contact the
hardware
> > vendor support to inquire about this issue. I believe that they will
> > assist
> > you best since they will have the proper material resources to resolve
> > this
> > problem.
> >
> > I hope the information is helpful.
> >
> >
> > Sophie Guo
> > Microsoft Online Partner Support
> >
> > Get Secure! - www.microsoft.com/security
> >
> > =====================================================> > 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.
> >
>|||I'm operating in exactly this configuration. As mentioned by others,
its really straight forward to setup:
Prerequsites:
- A Sql Server 2000 Enterprise instance with SP3a
Installation:
1) Install Sql Reporting 2000 Enterprise on the first web server.
During installation it creates the needed ReportServer and
ReportServerTempDb databases.
2) Install Sql Reporting 2000 Enterprise on each subsequent server in
Farm and point them at the ReportServer DB created in step 1. (repeat
for each additional server)
3) Deploy RDL's via ReportsServer web service from any of the servers
(since they share the same DB and therefore will share the RDL's once
they are uploaded).
4) Start using your servers. (or begin applying Service packs)
Note: SP2 will require one extra step which is to run RSActivate in
order to join your additional Report Server nodes to the group. In
pre-SP2 installations, this is done automatically for you.
One thing to consider when doing the F5 setup; make sure to setup
Server Affinity using a time-based session so you don't run into any
problems with ASP.NET post-backs. Typically I set the session
expiration to 40 minutes, but it all depends upon your
user-characteristics. Also I have found it helpful to utilize the
"Least Used" algorithm rather than the default "Round Robin" approach
to load balancing.
Obviously, there are numerous architectural and infrastructural
decisions required throughout this process, but this should give you
the 10k meter view.
I am happy with F5 for load balancing so far, so I hope this works out
for you.
Enjoy.
Lance Hunt
http://weblogs.asp.net/lhunt/|||Hello Adrian,
For the second item:
2. Deploy any subsequent nodes by joining the nodes to the initial
reporting services node by specifying the RSWEBFARMSERVER property in the
installation
The RSWEBFARMSERVER property is specified in the command prompt. To install
a web farm, you have to specify the RSDATABASENAME and RSDATABASESERVER
property in the command prompt.
For more information, please refer to the following topic in BOL:
"Installing Reporting Services From the Command Line"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
tm/gs_installingrs_v1_6h6h.asp
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================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.|||Hi!
I'm also F5 Hardware load balancing, but I'm running into a problem.
Right now, we have 2 web servers in a cluster, and an F5 load balancer
infront of it. Both web servers have Kerberos delegation enabled, and
I can access Reporting services via Web Service just fine when I access
the web servers directly. However, when I put the F5 load balancer
infront, I get an Authentication error. The load balancer appears to
be sending my credentials as Anonymous! Has this happened to anyone?
Is there a Kerberos setting on this F5 hardware load balancer? I'm
unfamiliar with the hardware, and I'm trying to contact my IT
department to contact the vendor. That might take a while. I'm hoping
someone here has an answer.
Thanks!
Roy Assaly
Sophie Guo [MSFT] wrote:
> Hello Adrian,
> For the second item:
> 2. Deploy any subsequent nodes by joining the nodes to the initial
> reporting services node by specifying the RSWEBFARMSERVER property in
the
> installation
> The RSWEBFARMSERVER property is specified in the command prompt. To
install
> a web farm, you have to specify the RSDATABASENAME and
RSDATABASESERVER
> property in the command prompt.
> For more information, please refer to the following topic in BOL:
> "Installing Reporting Services From the Command Line"
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/h
> tm/gs_installingrs_v1_6h6h.asp
> I hope the information is helpful.
> Sophie Guo
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> =====================================================> 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.
Wednesday, March 21, 2012
Deployment error -- Incorrect ImpersonationInfo object
Hi,
I'm new to SSAS 2005 and I'm walking through the Analysis Services tutorial in the online documentation. So far so good until when I wanted to deploy the project. The error is
Error 1 Parser: The syntax for the ImpersonationInfo object is incorrect. If the ImpersonateAccount value is used for ImpersonationInfo, then the Account property cannot be empty. 0 0
I don't know why it asked for ImpersonationInfo. I'm a local administrator of the computer and I want to deploy to local server.
However, when I went through the Deployment Wizard in Analysis Services, it was deployed successfully. When I switched back to Visual Studio AS project and tried to browse the cube or dimension, it failed again saying that
Either the user, [UserID], does not have access to the Analysis Services Tutorial database, or the database does not exist.
What am I missing? :(
Thanks
JennyNevermind. I've figured it out myself. I forgot to deploy the Adventure Works DW analysis services project first. Also, when I set up the data source, for some reasons, impersonation was selected by mistake.
Thanks!|||Hi Jenny Tam.
I had the same error. here is how to correct it
1-right-click on data source in solution explorer
2-select View Designer
3-select Impersonation Information tab, then Default box
It's all.|||Thanks - I have the same problem and it is great solution.
|||thank you
Deployment error -- Incorrect ImpersonationInfo object
Hi,
I'm new to SSAS 2005 and I'm walking through the Analysis Services tutorial in the online documentation. So far so good until when I wanted to deploy the project. The error is
Error 1 Parser: The syntax for the ImpersonationInfo object is incorrect. If the ImpersonateAccount value is used for ImpersonationInfo, then the Account property cannot be empty. 0 0
I don't know why it asked for ImpersonationInfo. I'm a local administrator of the computer and I want to deploy to local server.
However, when I went through the Deployment Wizard in Analysis Services, it was deployed successfully. When I switched back to Visual Studio AS project and tried to browse the cube or dimension, it failed again saying that
Either the user, [UserID], does not have access to the Analysis Services Tutorial database, or the database does not exist.
What am I missing? :(
Thanks
JennyNevermind. I've figured it out myself. I forgot to deploy the Adventure Works DW analysis services project first. Also, when I set up the data source, for some reasons, impersonation was selected by mistake.
Thanks!|||Hi Jenny Tam.
I had the same error. here is how to correct it
1-right-click on data source in solution explorer
2-select View Designer
3-select Impersonation Information tab, then Default box
It's all.|||Thanks - I have the same problem and it is great solution.
|||thank you
Deployment error -- Incorrect ImpersonationInfo object
Hi,
I'm new to SSAS 2005 and I'm walking through the Analysis Services tutorial in the online documentation. So far so good until when I wanted to deploy the project. The error is
Error 1 Parser: The syntax for the ImpersonationInfo object is incorrect. If the ImpersonateAccount value is used for ImpersonationInfo, then the Account property cannot be empty. 0 0
I don't know why it asked for ImpersonationInfo. I'm a local administrator of the computer and I want to deploy to local server.
However, when I went through the Deployment Wizard in Analysis Services, it was deployed successfully. When I switched back to Visual Studio AS project and tried to browse the cube or dimension, it failed again saying that
Either the user, [UserID], does not have access to the Analysis Services Tutorial database, or the database does not exist.
What am I missing? :(
Thanks
JennyNevermind. I've figured it out myself. I forgot to deploy the Adventure Works DW analysis services project first. Also, when I set up the data source, for some reasons, impersonation was selected by mistake.
Thanks!|||Hi Jenny Tam.
I had the same error. here is how to correct it
1-right-click on data source in solution explorer
2-select View Designer
3-select Impersonation Information tab, then Default box
It's all.|||Thanks - I have the same problem and it is great solution.
|||thank you
Friday, March 9, 2012
Deploying MSDE200 w/ app
I need to deploy my msde2000 database with an application
using Wise Install. If you've done this before, do you
have any documentation or procedures to set this up? I
would greatly appreciate any help on this.
Thanks in advance,
George
greda@.msn.com
Thanks for your help. I'll check out the links.
George
>--Original Message--
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/dnmsde/html/msdedepl.asp
>Check out that website, it has a tutorial on using MS'
MSDE Bootstrapper. This site has useful info on how to
actually tap into the app's installation events and
script a database/drop a database. I personally used a
bootstrap program I found here:
>http://www.codeproject.com/dotnet/dotNetInstaller.asp?
target=dotNetInstaller
>I could never figure out exactly how to use the
Microsoft MSDE Bootstrapper, very very poorly documented,
while the example on how to use it was decent, it seemed
it was skirting past the basics, like instructing whether
the MSDE path you specify is to the correct .MSI, or
Setup.EXE, or whether it worked against MSDE2000 release
A or not, and it never pointed out how to set a
bootstrapper in a projects configuration. Really poor
documentation, I'm sure it's great if you know exactly
how the heck it works. I can't get past that, so some
Italian kid sold me on his bootstrapper, which for
usability and flexibility, it far surpasses the Microsoft
MSDE Bootstrapper.
>My 2 cents.
>.
>
|||Thanks for your help Jim. I'll follow your instructions.
if you have any sample code I can look at, that would
help me tremendously. Its my first time deploying a
product using MSDE2000. I'm wondering how you would
handle multiple users? One CD with MSDE2000 and another
with the client software?
Thanks. George
>--Original Message--
>I've had to do exactly what you are try to accomplish.
>Our company produces and distributes a MSDE based
client - server
>application and we use Wise for the installation
platform. The installation
>process is separated into three stages: 1) Install MSDE
2) Install our
>database and configure users and permissions 3) Install
the application.
>Here's a brief description of what we do.
>For Stage 1 I developed a Wise scritp for installing
MSDE using the MSDE
>setup.exe program. I gather all the need parameters from
the installing user
>and then bootstrap
>setup.exe, install a named instance of MSDE, and wait
for it to exit. I
>examine the return value from the process to see if the
installation
>succeded. If it did I then put a value in the registry
to have the next
>stage of the installation run automatically when the
system reboots. I then
>force a reboot of the system. I make no attempt to try
to make the
>installation of MSDE seamless or not require a reboot,
as most times a
>reboot is required before SQL Server will run. For
Windows 9x systems I then
>install a small executable that runs at boot time and
that will start up SQL
>Server (there are no services in Win9x), rather than
trying to configure
>something in the Startup folder.
>Stage 2 - In my next Wise script I look for my named
instance of MSDE. I've
>written a helper DLL that uses SQL-DMO and T-SQL to
provide a number of
>needed functions for doing preliminary database
configuration such as
>searching for runnning instances of SQL Server,
attaching the database,
>creating logins and such. If I find my instance then I
connect to it using
>the sa account, copy the database from the installation
source to the data
>directory of MSDE and attach it. I then create the
needed logins for the
>application. This current application uses ODBC (the
next version will use
>ADO) so I then create an system ODBC connection for the
application. To do
>this I run the user through the ODBC wizard (Wise can
fire this off for you)
>so that the user can determine that the connection is
valid and works.
>Stage 3 - Install the client application. This is a just
a straight forward
>application installation.
>Our product is installed on hundred of systems and the
installation process[vbcol=seagreen]
>has a very low failure or problem rate.
>Jim
>"George" <greda@.msn.com> wrote in message
>news:1912001c44ca9$e6dc0760$a301280a@.phx.gbl...
application
>
>.
>
using Wise Install. If you've done this before, do you
have any documentation or procedures to set this up? I
would greatly appreciate any help on this.
Thanks in advance,
George
greda@.msn.com
Thanks for your help. I'll check out the links.
George
>--Original Message--
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/dnmsde/html/msdedepl.asp
>Check out that website, it has a tutorial on using MS'
MSDE Bootstrapper. This site has useful info on how to
actually tap into the app's installation events and
script a database/drop a database. I personally used a
bootstrap program I found here:
>http://www.codeproject.com/dotnet/dotNetInstaller.asp?
target=dotNetInstaller
>I could never figure out exactly how to use the
Microsoft MSDE Bootstrapper, very very poorly documented,
while the example on how to use it was decent, it seemed
it was skirting past the basics, like instructing whether
the MSDE path you specify is to the correct .MSI, or
Setup.EXE, or whether it worked against MSDE2000 release
A or not, and it never pointed out how to set a
bootstrapper in a projects configuration. Really poor
documentation, I'm sure it's great if you know exactly
how the heck it works. I can't get past that, so some
Italian kid sold me on his bootstrapper, which for
usability and flexibility, it far surpasses the Microsoft
MSDE Bootstrapper.
>My 2 cents.
>.
>
|||Thanks for your help Jim. I'll follow your instructions.
if you have any sample code I can look at, that would
help me tremendously. Its my first time deploying a
product using MSDE2000. I'm wondering how you would
handle multiple users? One CD with MSDE2000 and another
with the client software?
Thanks. George
>--Original Message--
>I've had to do exactly what you are try to accomplish.
>Our company produces and distributes a MSDE based
client - server
>application and we use Wise for the installation
platform. The installation
>process is separated into three stages: 1) Install MSDE
2) Install our
>database and configure users and permissions 3) Install
the application.
>Here's a brief description of what we do.
>For Stage 1 I developed a Wise scritp for installing
MSDE using the MSDE
>setup.exe program. I gather all the need parameters from
the installing user
>and then bootstrap
>setup.exe, install a named instance of MSDE, and wait
for it to exit. I
>examine the return value from the process to see if the
installation
>succeded. If it did I then put a value in the registry
to have the next
>stage of the installation run automatically when the
system reboots. I then
>force a reboot of the system. I make no attempt to try
to make the
>installation of MSDE seamless or not require a reboot,
as most times a
>reboot is required before SQL Server will run. For
Windows 9x systems I then
>install a small executable that runs at boot time and
that will start up SQL
>Server (there are no services in Win9x), rather than
trying to configure
>something in the Startup folder.
>Stage 2 - In my next Wise script I look for my named
instance of MSDE. I've
>written a helper DLL that uses SQL-DMO and T-SQL to
provide a number of
>needed functions for doing preliminary database
configuration such as
>searching for runnning instances of SQL Server,
attaching the database,
>creating logins and such. If I find my instance then I
connect to it using
>the sa account, copy the database from the installation
source to the data
>directory of MSDE and attach it. I then create the
needed logins for the
>application. This current application uses ODBC (the
next version will use
>ADO) so I then create an system ODBC connection for the
application. To do
>this I run the user through the ODBC wizard (Wise can
fire this off for you)
>so that the user can determine that the connection is
valid and works.
>Stage 3 - Install the client application. This is a just
a straight forward
>application installation.
>Our product is installed on hundred of systems and the
installation process[vbcol=seagreen]
>has a very low failure or problem rate.
>Jim
>"George" <greda@.msn.com> wrote in message
>news:1912001c44ca9$e6dc0760$a301280a@.phx.gbl...
application
>
>.
>
Subscribe to:
Posts (Atom)