Thursday, March 29, 2012
Does SRS sql engine break things that used to work?
the sqlservr executable is at build 8.00.760 and install SRS I get a new
build of the sql engine.
SQLServr.EXE build is 8.00.859 in SRS and things that used to work don't.
For example, stored procedure debug doesn't work at all on an SRS SQL Server.
I know I have seen a few other things that are now broke.
Does anyone know of any hotfixes that repair features that SRS breaks?RS doesn't do anything to the SQL Engine. If you are talkin about the 859
hotfix that we require in certain situations, there is a newer hotfix that
resolves the problem. You need to request it from product support. See
http://support.microsoft.com/default.aspx?scid=kb;en-us;831997.
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:22305D8C-975B-4283-BC11-8264CDDEEB1E@.microsoft.com...
> I've noticed that when I take stable SQL 2000 engines that are at SP3A
> where
> the sqlservr executable is at build 8.00.760 and install SRS I get a new
> build of the sql engine.
> SQLServr.EXE build is 8.00.859 in SRS and things that used to work don't.
> For example, stored procedure debug doesn't work at all on an SRS SQL
> Server.
> I know I have seen a few other things that are now broke.
> Does anyone know of any hotfixes that repair features that SRS breaks?|||Thank-you for the quick reponse Brian.
I think maybe I wasn't too clear on my question.
If I install SQL Server 2000 Standard and then take it up to SP3A the build
level of my SQL engine is 760.
However, if I then apply SQL Reporting Services on top of this installation
my SQL engine gets taken up to build 859. Maybe this is not directly related
to SRS, but it certainly takes place upon installation of SRS.
At that point I no longer have the capability to debug stored procs (I
believe thru the sp_dbidbg xp).
So the downside is that I have to make a choice between having SRS and then
losing the capability of stored proc debug or not having SRS.
If there is a hotfix that addresses that I would love to have it.
thanks,
dan
"Brian Welcker [MS]" wrote:
> RS doesn't do anything to the SQL Engine. If you are talkin about the 859
> hotfix that we require in certain situations, there is a newer hotfix that
> resolves the problem. You need to request it from product support. See
> http://support.microsoft.com/default.aspx?scid=kb;en-us;831997.
>
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Dan" <Dan@.discussions.microsoft.com> wrote in message
> news:22305D8C-975B-4283-BC11-8264CDDEEB1E@.microsoft.com...
> > I've noticed that when I take stable SQL 2000 engines that are at SP3A
> > where
> > the sqlservr executable is at build 8.00.760 and install SRS I get a new
> > build of the sql engine.
> >
> > SQLServr.EXE build is 8.00.859 in SRS and things that used to work don't.
> >
> > For example, stored procedure debug doesn't work at all on an SRS SQL
> > Server.
> >
> > I know I have seen a few other things that are now broke.
> >
> > Does anyone know of any hotfixes that repair features that SRS breaks?
>
>|||The RS setup proces does not touch the version of the SQL engine. We really
don't. We recommend a specific SQL engine hotfix during the installation
process that does do this. You would need to call product support for the
hotfix. I don't think it is generally downloadable.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:DA304849-A7E9-4A92-A39D-5E338227EF52@.microsoft.com...
> Thank-you for the quick reponse Brian.
> I think maybe I wasn't too clear on my question.
> If I install SQL Server 2000 Standard and then take it up to SP3A the
> build
> level of my SQL engine is 760.
> However, if I then apply SQL Reporting Services on top of this
> installation
> my SQL engine gets taken up to build 859. Maybe this is not directly
> related
> to SRS, but it certainly takes place upon installation of SRS.
> At that point I no longer have the capability to debug stored procs (I
> believe thru the sp_dbidbg xp).
> So the downside is that I have to make a choice between having SRS and
> then
> losing the capability of stored proc debug or not having SRS.
> If there is a hotfix that addresses that I would love to have it.
> thanks,
> dan
>
> "Brian Welcker [MS]" wrote:
>> RS doesn't do anything to the SQL Engine. If you are talkin about the 859
>> hotfix that we require in certain situations, there is a newer hotfix
>> that
>> resolves the problem. You need to request it from product support. See
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;831997.
>>
>> --
>> Brian Welcker
>> Group Program Manager
>> Microsoft SQL Server
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Dan" <Dan@.discussions.microsoft.com> wrote in message
>> news:22305D8C-975B-4283-BC11-8264CDDEEB1E@.microsoft.com...
>> > I've noticed that when I take stable SQL 2000 engines that are at SP3A
>> > where
>> > the sqlservr executable is at build 8.00.760 and install SRS I get a
>> > new
>> > build of the sql engine.
>> >
>> > SQLServr.EXE build is 8.00.859 in SRS and things that used to work
>> > don't.
>> >
>> > For example, stored procedure debug doesn't work at all on an SRS SQL
>> > Server.
>> >
>> > I know I have seen a few other things that are now broke.
>> >
>> > Does anyone know of any hotfixes that repair features that SRS breaks?
>>sql
Thursday, March 22, 2012
Does RS use the MS FullText Search Engine?
Technology Department.
Somehow the SQL Server instance where the Report Server databases were got
dettached. They were able to re-enable it, but they cannot restart this
engine because of a corrupt configuration file.
They are asking me whether they should keep researching and trying to fix
this file or they can just remove the engine from the cluster.
Thanks!
Ray G.The FullText search engine is not used by RS.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"RayG" <RayG@.discussions.microsoft.com> wrote in message
news:44515EB2-37F2-4073-B085-023B8051A788@.microsoft.com...
> Not sure what this question means, but I am being asked this by our
> Technology Department.
> Somehow the SQL Server instance where the Report Server databases were got
> dettached. They were able to re-enable it, but they cannot restart this
> engine because of a corrupt configuration file.
> They are asking me whether they should keep researching and trying to fix
> this file or they can just remove the engine from the cluster.
> Thanks!
> Ray G.
Friday, February 17, 2012
Document properties
developing. How can we search on the properties of the document such as size
or date created as well as preforming a full text search?
The iFilters used in SQL FTS do not emit the document properties like size,
creation date, modified date. You will have to store them in the database in
seperate columns.
Ie
Create Table Text
(pk int not null primary key identity(1,1),
CreateDate datetime,
Size int,
TextCol text
)
Querying is difficult, as you typically want to limit your results set to
the top 100 for performance reasons. So your query would look like this:
select * from text join containstable(text, *, 'Microsoft',100) as a
on a.[key]=text.pk
where createdate> getdate()-20
order by rank desc
The problem is lets suppose the top 100 ranked hits on Microsoft are all
more recent than getdate()-20. In this case you will get no hits to such a
query.
There is a performance penalty to pay for returning more than 2000 hits from
MSSearch in a query. The workaround is to try an expensive query like this
and hope you get a small results set returned from MSSearch:
select * from text join containstable(text, *, 'Microsoft') as a
on a.[key]=text.pk
where createdate> getdate()-20
order by rank desc
or to partition your text table into date ranges which match your search
criteria.
The same sort of logic applies for size.
For small tables this won't be a problem for you. For large tables it is a
problem.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Rob 19" <Rob19@.discussions.microsoft.com> wrote in message
news:77698456-55A4-44DC-A67A-844A64F66685@.microsoft.com...
> I am using FTI as a search engine in a document library that we are
> developing. How can we search on the properties of the document such as
size
> or date created as well as preforming a full text search?
|||Thanks Hilary. Do we know if this problem will be addressed in SQL Server 2005?
"Hilary Cotter" wrote:
> The iFilters used in SQL FTS do not emit the document properties like size,
> creation date, modified date. You will have to store them in the database in
> seperate columns.
> Ie
> Create Table Text
> (pk int not null primary key identity(1,1),
> CreateDate datetime,
> Size int,
> TextCol text
> )
> Querying is difficult, as you typically want to limit your results set to
> the top 100 for performance reasons. So your query would look like this:
> select * from text join containstable(text, *, 'Microsoft',100) as a
> on a.[key]=text.pk
> where createdate> getdate()-20
> order by rank desc
> The problem is lets suppose the top 100 ranked hits on Microsoft are all
> more recent than getdate()-20. In this case you will get no hits to such a
> query.
> There is a performance penalty to pay for returning more than 2000 hits from
> MSSearch in a query. The workaround is to try an expensive query like this
> and hope you get a small results set returned from MSSearch:
> select * from text join containstable(text, *, 'Microsoft') as a
> on a.[key]=text.pk
> where createdate> getdate()-20
> order by rank desc
> or to partition your text table into date ranges which match your search
> criteria.
> The same sort of logic applies for size.
> For small tables this won't be a problem for you. For large tables it is a
> problem.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> "Rob 19" <Rob19@.discussions.microsoft.com> wrote in message
> news:77698456-55A4-44DC-A67A-844A64F66685@.microsoft.com...
> size
>
>
|||No, its still a problem.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Rob 19" <Rob19@.discussions.microsoft.com> wrote in message
news:BA69E42E-7999-4165-9547-5D4BECC3997E@.microsoft.com...
> Thanks Hilary. Do we know if this problem will be addressed in SQL Server
2005?[vbcol=seagreen]
> "Hilary Cotter" wrote:
size,[vbcol=seagreen]
database in[vbcol=seagreen]
to[vbcol=seagreen]
a[vbcol=seagreen]
from[vbcol=seagreen]
this[vbcol=seagreen]
a[vbcol=seagreen]
as[vbcol=seagreen]
Tuesday, February 14, 2012
Do you need 1 or 2 SQL licenses to install RS on separate web server?
Plese help with this issue by reading and responding!!!
If you install Reporting Services 2005 on a separate web server from the database engine do you need 1 or 2 SQL licenses? It's a more complex issue than it initially appears to be. Please go to the following thread and read the bottom of page 1 and page 2.
Please help verify this! Page 2 contains a post with 5 steps that you can perform to verify that only 1 license is actually need!
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=198900&SiteID=1
Note: Unfortunately this discussion got started in a off topic thread in the wrong category. I wrote this thread so that interested people could find it.
I am pretty sure that you need a license for each if you separate them. This is a scenerio page from MS:
http://www.microsoft.com/sql/howtobuy/howtolicensers.mspx
|||steveareno,The "license.txt" file that ships on the SQL 2005 install disks says the exact opposite.
Thanks,
Greg
|||I'm shocked by the lack of interest in this. SQL licenses are quite expensive after all.
Is anyone out there planning to run Reporting Services on a separate server from the SQL database engine? I figued that would be a common configuration but maybe I'm wrong?
Thanks,
Greg Van Mullem
|||I'm puzzled as to what more information you're looking for. The information in the link provided bysteveareno tells you all you need to know.|||I found out the answer to my question. Here it is:
You only need 1 SQL license to install RS 2005 on a separate web server!
Thanks for the help with this it's quite confusing because some of the docs on Microsoft's web site are bogus! Read the "license.txt" file that ships on the SQL 2005 standard edition disk if you don't believe me.
Thanks,
Greg Van Mullem
Do you need 1 or 2 SQL licenses to install RS on separate web server?
Plese help with this issue by reading and responding!!!
If you install
Reporting Services 2005 on a separate web server from the database engine do you
need 1 or 2 SQL licenses? It's a more complex issue than it initially appears to
be. Please go to the following thread and read the bottom of page 1 and page
2.
Please help verify this! Page 2 contains a post with 5
steps that you can perform to verify that only 1 license is actually
need!
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=198900&SiteID=1
Note: Unfortunately this discussion got started in a
off topic thread in the wrong category. I wrote this thread so that interested
people could find it.
I am pretty sure that you need a license for each if you separate them. This is a scenerio page from MS:
http://www.microsoft.com/sql/howtobuy/howtolicensers.mspx
|||steveareno,The "license.txt" file that ships on the SQL 2005 install disks says the exact opposite.
Thanks,
Greg|||I'm shocked by the lack of interest in this. SQL licenses are quite expensive after all.
Is anyone out there planning to run Reporting Services on a separate server from the SQL database engine? I figued that would be a common configuration but maybe I'm wrong?
Thanks,
Greg Van Mullem|||I'm puzzled as to what more information you're looking for. The information in the link provided by steveareno tells you all you need to know.|||I found out the answer to my question. Here it is:
You only need 1 SQL license to install RS 2005 on a separate web server!
Thanks for the help with this it's quite confusing because some of the docs on Microsoft's web site are bogus!
Read the "license.txt" file that ships on the SQL 2005 standard edition disk if you don't believe me.
Thanks,
Greg Van Mullem