Wednesday, March 21, 2012
installed msde database server desktop edition and well...
Monday, March 19, 2012
Installation SQL 2005 Express from a network
Perhaps these will help:
SQL Server 2005 UnAttended Installations
http://msdn2.microsoft.com/en-us/library/ms144259.aspx
http://www.devx.com/dbzone/Article/31648
As far as I am aware, there is no direct support for Enterprise use of SQL Express, including push installations. Think about it. Why would a company go to much trouble (and expense) creating an advanced tool to allow you to use a free product.
SQL Express is not positioned as an Enterprise product.
|||Thank you Arnie we will check out that article. Yea I know but we have corp. customers who want to deply SQL Express to workstations from the network and not use pull so we are trying to please them.Friday, March 9, 2012
Installation Of SSRS
Server and IIS installed on it and Machine B is the web server. Machine B
does not have Sql Server.
Is there any way by which I can upload my .rdl files on Machine B ie; create
the virtual folders (Reports and ReportsServer) on Machine B?
TIAafraid not as far as I know. When you deploy the reports the rdl files
are actually stored in the reporting services database, which is on
machine A. They aren't stored as physical files on your web server /
Machine B.
A further problem - if you're using RS 200 - is that the web server
will have to have an instance of SQL server installed on it, as the
reporting services database has to be on the same machine as the web
project. Sounds crazy I know but that's the way it is.|||This is so wrong. You DO NOT have to have SQL Server installed where RS is
installed. A quick primer.
RS is an asp.net application. It uses SQL Server as its metadata/object
store. SQL Server can be either on the same machine or on another machine
(this is true for both RS 2000 and RS 2005). If you have Enterprise you can
support a web farm. Several RS servers all sharing the same database (this
means reports, subscriptions, security, etc is setup once for the whole web
farm deployment).
Licensing is a different matter. Any box that has RS installed needs a SQL
Server license, just the same as if you do have SQL Server on the box.
My preference is to have SQL Server on the same box even if my data is
somewhere else. It doesn't cost any more and then my metadata/object storage
is on the same machine as RS. However, again, you do not have to do this.
Note, if the intention is to integrate RS with your own web app you should
really really consider RS 2005. RS 2005 does not require a SQL Server 2005
database, it can use SQL Server 2000 database BUT you do have to buy a SQL
Server 2005 license for the box running RS. VS 2005 has two new controls
that work only with RS 2005: a web form and a winform control. The webform
control makes integration much easier and it is easier to get fuller
functionality quicker than anything you could do with RS 2000.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Gearóid" <ghealy@.gmail.com> wrote in message
news:1146818234.435496.208080@.i39g2000cwa.googlegroups.com...
> afraid not as far as I know. When you deploy the reports the rdl files
> are actually stored in the reporting services database, which is on
> machine A. They aren't stored as physical files on your web server /
> Machine B.
> A further problem - if you're using RS 200 - is that the web server
> will have to have an instance of SQL server installed on it, as the
> reporting services database has to be on the same machine as the web
> project. Sounds crazy I know but that's the way it is.
>|||I tried to change the name of the instance of SQL server while installing
SSRS, but it is givinng me error "Login Failed for Guest". I can login to the
Query Analyzer from this remote machine but SSRS is not allowing to connect.
What is the proper way of assiging user name and pwd while installing SSRS.
Do I have to make changes to logins and users on the sql machine.
"Bruce L-C [MVP]" wrote:
> This is so wrong. You DO NOT have to have SQL Server installed where RS is
> installed. A quick primer.
> RS is an asp.net application. It uses SQL Server as its metadata/object
> store. SQL Server can be either on the same machine or on another machine
> (this is true for both RS 2000 and RS 2005). If you have Enterprise you can
> support a web farm. Several RS servers all sharing the same database (this
> means reports, subscriptions, security, etc is setup once for the whole web
> farm deployment).
> Licensing is a different matter. Any box that has RS installed needs a SQL
> Server license, just the same as if you do have SQL Server on the box.
> My preference is to have SQL Server on the same box even if my data is
> somewhere else. It doesn't cost any more and then my metadata/object storage
> is on the same machine as RS. However, again, you do not have to do this.
> Note, if the intention is to integrate RS with your own web app you should
> really really consider RS 2005. RS 2005 does not require a SQL Server 2005
> database, it can use SQL Server 2000 database BUT you do have to buy a SQL
> Server 2005 license for the box running RS. VS 2005 has two new controls
> that work only with RS 2005: a web form and a winform control. The webform
> control makes integration much easier and it is easier to get fuller
> functionality quicker than anything you could do with RS 2000.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Gearóid" <ghealy@.gmail.com> wrote in message
> news:1146818234.435496.208080@.i39g2000cwa.googlegroups.com...
> > afraid not as far as I know. When you deploy the reports the rdl files
> > are actually stored in the reporting services database, which is on
> > machine A. They aren't stored as physical files on your web server /
> > Machine B.
> >
> > A further problem - if you're using RS 200 - is that the web server
> > will have to have an instance of SQL server installed on it, as the
> > reporting services database has to be on the same machine as the web
> > project. Sounds crazy I know but that's the way it is.
> >
>
>
Friday, February 24, 2012
Installation Hangs when on a large network
Hi All,
I have to do a lot of SQL Server Express 2005 installations and I've noticed that when I'm doing an install on a machine that's on a large network that the installer will "hang" towards the end of the installation process. The installer will say something about Local Groups and sit there for a really long time. As soon as I take the machine off of the network though (via unplugging the network cable) the installer jumps back into action. Of course, I've not seen this on a stand alone machine either...
It would seem to me that the installer is trying to communicate via the network or something and then when it loses its LAN access it just moves on. But I'm not entirely sure why it would need to do that. More importantly, is there a way that I can keep it from doing this? I'm doing a silent install so maybe I can use a command line swith or property?
In reviewing the command line options I didn't see much that seemed to fit; but perhaps one of you folks know of a way to achieve this.
Thank you for anything you can offer.
SQL Server and other RDBMS are best installed from the C drive of the box you are installing it, that is copy all files to the C drive and run setup from the C drive. I have installed it as a member of 150, 000 employees network and at least 1,000 are .NET developers without issues. Hope this helps.Installation Hangs when on a large network
Hi All,
I have to do a lot of SQL Server Express 2005 installations and I've noticed that when I'm doing an install on a machine that's on a large network that the installer will "hang" towards the end of the installation process. The installer will say something about Local Groups and sit there for a really long time. As soon as I take the machine off of the network though (via unplugging the network cable) the installer jumps back into action. Of course, I've not seen this on a stand alone machine either...
It would seem to me that the installer is trying to communicate via the network or something and then when it loses its LAN access it just moves on. But I'm not entirely sure why it would need to do that. More importantly, is there a way that I can keep it from doing this? I'm doing a silent install so maybe I can use a command line swith or property?
In reviewing the command line options I didn't see much that seemed to fit; but perhaps one of you folks know of a way to achieve this.
Thank you for anything you can offer.
SQL Server and other RDBMS are best installed from the C drive of the box you are installing it, that is copy all files to the C drive and run setup from the C drive. I have installed it as a member of 150, 000 employees network and at least 1,000 are .NET developers without issues. Hope this helps.Sunday, February 19, 2012
Installation Error
Here are a couple of things to try:
1. Check the installation log files, located at %Program
Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files for more
details on the error. (Search for the text string "value 3" to get to the failed log)
2. Try to add the service manually to the local groups using the Computer Management Admin tool. Then re-run setup.
Thanks,
Sam Lester (MSFT)
Installation Error
Here are a couple of things to try:
1. Check the installation log files, located at %Program
Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files for more
details on the error. (Search for the text string "value 3" to get to the failed log)
2. Try to add the service manually to the local groups using the Computer Management Admin tool. Then re-run setup.
Thanks,
Sam Lester (MSFT)