Parameter Limitations?

Hi all,
I am calling a SP from RS inwhich there is an optional parameter of string
type. I allow the parameter to be blank and the results returned are
correct. When i try to filter my results by adding a name (ie Tic-Tot's
Daycare) and run the preview again the results are the same as if i left the
parameter blank. When i run the SP in the data view and include the name it
returns the filtered results. When i run the SP in QA i get the filtered
result. My only thought is the odd chars in the string ( single quote and
hyphen) could be messing up the parameter passing. Can some one please
confirm this or give a different suggestion for this issue.
Thanks in advance,
SPOSince the string delimiter in SQL is a single quote, I would suspect that is
your problem... You might try to double up on single quotes in your
parameters ,( which escapes the quote in SQL)... First eliminate the quote
from the parameter and see if it works...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"iamspo" <iamspo@.discussions.microsoft.com> wrote in message
news:5097986A-9711-4802-B839-9BB7A8C22F49@.microsoft.com...
> Hi all,
> I am calling a SP from RS inwhich there is an optional parameter of string
> type. I allow the parameter to be blank and the results returned are
> correct. When i try to filter my results by adding a name (ie Tic-Tot's
> Daycare) and run the preview again the results are the same as if i left
> the
> parameter blank. When i run the SP in the data view and include the name
> it
> returns the filtered results. When i run the SP in QA i get the filtered
> result. My only thought is the odd chars in the string ( single quote and
> hyphen) could be messing up the parameter passing. Can some one please
> confirm this or give a different suggestion for this issue.
> Thanks in advance,
> SPO|||I actually found the error. Since i added the name filter parameter as a
second version to this SP it was not picked up by RS. I went in and added
the parameter (report => report parameters...) but never went back and added
it to the parameter list in the data set. Once i did think the data set knew
which parameter to associate this value to and sent it to the SP. The result
returned were correct, none of the special char's used caused an issue.
Thanks for the help!!!
"iamspo" wrote:
> Hi all,
> I am calling a SP from RS inwhich there is an optional parameter of string
> type. I allow the parameter to be blank and the results returned are
> correct. When i try to filter my results by adding a name (ie Tic-Tot's
> Daycare) and run the preview again the results are the same as if i left the
> parameter blank. When i run the SP in the data view and include the name it
> returns the filtered results. When i run the SP in QA i get the filtered
> result. My only thought is the odd chars in the string ( single quote and
> hyphen) could be messing up the parameter passing. Can some one please
> confirm this or give a different suggestion for this issue.
> Thanks in advance,
> SPO

Parameter calendar control : week start date

With Reporting Services (SQL Server 2005), if you include a parameter with a
data type of DateTime, you get a calendar control for the parameter on your
report.
How do you change the first day of the week from Sunday to Monday?
Thanks,
CraigIs your question related to calender control, because you have asked
seperately,
in fact you cant change the calender control. Ofcourse in sql server yes you
can by giving
SET DATEFIRST 1 (Monday)
SET DATEFIRST 7 (Sunday - Default)
Amarnath
"CraigHB" wrote:
> With Reporting Services (SQL Server 2005), if you include a parameter with a
> data type of DateTime, you get a calendar control for the parameter on your
> report.
> How do you change the first day of the week from Sunday to Monday?
> Thanks,
> Craig

'PAGEIOLATCH_SH

In current activity i have a wait type of 'PAGEIOLATCH_SH'
BOL and other sources make no referance to this.
Can any body help?Hi
Google does though!!
Try:
http://www.sqldev.net/misc/waittypes.htm
John
"Mat" <anonymous@.discussions.microsoft.com> wrote in message
news:1ee9301c4577b$3f2d8c00$a301280a@.phx
.gbl...
> In current activity i have a wait type of 'PAGEIOLATCH_SH'
> BOL and other sources make no referance to this.
> Can any body help?|||I have heard that this might also indicate contention due to a large number
of indexes on the same table...
(although I personally have not encountered it)
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mat" <anonymous@.discussions.microsoft.com> wrote in message
news:1ee9301c4577b$3f2d8c00$a301280a@.phx
.gbl...
> In current activity i have a wait type of 'PAGEIOLATCH_SH'
> BOL and other sources make no referance to this.
> Can any body help?|||I've encountered this.
I may be talking out of my 4th-Point-Of-Contact, but it can also be attribut
ed to multi-processor machines and faulty optimization
(parallelism). I've worked around it by applying the optimizer option MAXDOP
.
http://www.sql-server-performance.com/case_studies.asp
http://support.microsoft.com/defaul...kb;EN-US;243589
http://www.databasejournal.com/feat...cle.php/1438891
ChrisG

'PAGEIOLATCH_SH

In current activity i have a wait type of 'PAGEIOLATCH_SH'
BOL and other sources make no referance to this.
Can any body help?Hi
Google does though!!
Try:
http://www.sqldev.net/misc/waittypes.htm
John
"Mat" <anonymous@.discussions.microsoft.com> wrote in message
news:1ee9301c4577b$3f2d8c00$a301280a@.phx.gbl...
> In current activity i have a wait type of 'PAGEIOLATCH_SH'
> BOL and other sources make no referance to this.
> Can any body help?|||I have heard that this might also indicate contention due to a large number
of indexes on the same table...
(although I personally have not encountered it)
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mat" <anonymous@.discussions.microsoft.com> wrote in message
news:1ee9301c4577b$3f2d8c00$a301280a@.phx.gbl...
> In current activity i have a wait type of 'PAGEIOLATCH_SH'
> BOL and other sources make no referance to this.
> Can any body help?|||I've encountered this.
I may be talking out of my 4th-Point-Of-Contact, but it can also be attributed to multi-processor machines and faulty optimization
(parallelism). I've worked around it by applying the optimizer option MAXDOP.
http://www.sql-server-performance.com/case_studies.asp
http://support.microsoft.com/default.aspx?scid=kb;EN-US;243589
http://www.databasejournal.com/features/mssql/article.php/1438891
ChrisG

'PAGEIOLATCH_SH

In current activity i have a wait type of 'PAGEIOLATCH_SH'
BOL and other sources make no referance to this.
Can any body help?
Hi
Google does though!!
Try:
http://www.sqldev.net/misc/waittypes.htm
John
"Mat" <anonymous@.discussions.microsoft.com> wrote in message
news:1ee9301c4577b$3f2d8c00$a301280a@.phx.gbl...
> In current activity i have a wait type of 'PAGEIOLATCH_SH'
> BOL and other sources make no referance to this.
> Can any body help?
|||I have heard that this might also indicate contention due to a large number
of indexes on the same table...
(although I personally have not encountered it)
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Mat" <anonymous@.discussions.microsoft.com> wrote in message
news:1ee9301c4577b$3f2d8c00$a301280a@.phx.gbl...
> In current activity i have a wait type of 'PAGEIOLATCH_SH'
> BOL and other sources make no referance to this.
> Can any body help?
|||I've encountered this.
I may be talking out of my 4th-Point-Of-Contact, but it can also be attributed to multi-processor machines and faulty optimization
(parallelism). I've worked around it by applying the optimizer option MAXDOP.
http://www.sql-server-performance.com/case_studies.asp
http://support.microsoft.com/default...b;EN-US;243589
http://www.databasejournal.com/featu...le.php/1438891
ChrisG