Default value or value provided for the report parameter 'ParamaterName' is
not a valid value. (rsInvalidReportParameter)
I am getting this error when I am trying to run a deployed report.
However,
this is driving me mad because in the report preview within VS.Net the
report
works fine and i can choose the same parameter settings from within the dev
environment with no problems. I am populating this parameter with a
dropdown
with valid values from a sproc (and this I've done a thousand times before)
.
I can not figure out why it is throwing this error, particularly since it
works perfectly fine in the preview pane. How could it be crappin out when
I
deploy it?!?! I am going insane!
Pl. put in forum.
regards
Arvind Sharma
--
Message posted via http://www.sqlmonster.comOn the deployed report, in report manager, properties... is the prompt string
blank? If so it will try to render the report without prompting for input
which will throw that error.
"arvind sharma via SQLMonster.com" wrote:
> Default value or value provided for the report parameter 'ParamaterName' is
> not a valid value. (rsInvalidReportParameter)
> I am getting this error when I am trying to run a deployed report.
> However,
> this is driving me mad because in the report preview within VS.Net the
> report
> works fine and i can choose the same parameter settings from within the dev
> environment with no problems. I am populating this parameter with a
> dropdown
> with valid values from a sproc (and this I've done a thousand times before)
> ..
> I can not figure out why it is throwing this error, particularly since it
> works perfectly fine in the preview pane. How could it be crappin out when
> I
> deploy it?!?! I am going insane!
> Pl. put in forum.
> regards
> Arvind Sharma
> --
> Message posted via http://www.sqlmonster.com
>sql
Showing posts with label provided. Show all posts
Showing posts with label provided. Show all posts
Monday, March 26, 2012
Wednesday, March 21, 2012
Microsoft Drivers for Accessing data from Unix.
Are there any microsoft provided ODBC drivers that can be installed on Unix
side for accessing SQL Server data? OR they are only available from third
party.
Regards,
MZeeshan
MS does not provide an ODBC driver that works on Unix. However, you can
get that from Data Direct. Microsoft does make a JDBC driver though.
MZeeshan wrote:
> Are there any microsoft provided ODBC drivers that can be installed on Unix
> side for accessing SQL Server data? OR they are only available from third
> party.
>
|||Hi MZeeshan,
Thanks for your post.
Unfortunately, I am sorry to say that we do not support ODBC drivers for
UNIX officially. However, I have noticed here is a very good article from
MVP Erland Sommarskog for your reference
Connecting to MS SQL Server from Unix
http://www.sommarskog.se/mssql/unix.html
Hope it helps.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
side for accessing SQL Server data? OR they are only available from third
party.
Regards,
MZeeshan
MS does not provide an ODBC driver that works on Unix. However, you can
get that from Data Direct. Microsoft does make a JDBC driver though.
MZeeshan wrote:
> Are there any microsoft provided ODBC drivers that can be installed on Unix
> side for accessing SQL Server data? OR they are only available from third
> party.
>
|||Hi MZeeshan,
Thanks for your post.
Unfortunately, I am sorry to say that we do not support ODBC drivers for
UNIX officially. However, I have noticed here is a very good article from
MVP Erland Sommarskog for your reference
Connecting to MS SQL Server from Unix
http://www.sommarskog.se/mssql/unix.html
Hope it helps.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Microsoft Drivers for Accessing data from Unix.
Are there any microsoft provided ODBC drivers that can be installed on Unix
side for accessing SQL Server data? OR they are only available from third
party.
Regards,
MZeeshanMS does not provide an ODBC driver that works on Unix. However, you can
get that from Data Direct. Microsoft does make a JDBC driver though.
MZeeshan wrote:
> Are there any microsoft provided ODBC drivers that can be installed on Uni
x
> side for accessing SQL Server data? OR they are only available from third
> party.
>|||Hi MZeeshan,
Thanks for your post.
Unfortunately, I am sorry to say that we do not support ODBC drivers for
UNIX officially. However, I have noticed here is a very good article from
MVP Erland Sommarskog for your reference
Connecting to MS SQL Server from Unix
http://www.sommarskog.se/mssql/unix.html
Hope it helps.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others: https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
side for accessing SQL Server data? OR they are only available from third
party.
Regards,
MZeeshanMS does not provide an ODBC driver that works on Unix. However, you can
get that from Data Direct. Microsoft does make a JDBC driver though.
MZeeshan wrote:
> Are there any microsoft provided ODBC drivers that can be installed on Uni
x
> side for accessing SQL Server data? OR they are only available from third
> party.
>|||Hi MZeeshan,
Thanks for your post.
Unfortunately, I am sorry to say that we do not support ODBC drivers for
UNIX officially. However, I have noticed here is a very good article from
MVP Erland Sommarskog for your reference
Connecting to MS SQL Server from Unix
http://www.sommarskog.se/mssql/unix.html
Hope it helps.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others: https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Wednesday, March 7, 2012
Meta Data cleanup
I have a quick question that I could not find the answer for anywhere.
The software developers that provided our SQL database program advised us to
put the subscription expiration on "never expire" because of their past
experience with customers who do not maintain their databases. Because of
this we now how massive meta data tables that need to be purged to increase
replkication performance (synchronization is extrmely slow). I have tried
setting the subscription retention to 14 days, but the amount of data to be
purged is huge and it interferes with the synchroniztion over night.
What I would like to do is use the stored procedure
sp_mergemetadataretentioncleanup to individually clean up the meta data
tables at each subscriber and the publisher. My problem is that I can not
find the parameters and correct syntax for this procedure anywhere. I have
seen the following:
sp_mergemetadataretentioncleanup (?,?,?)
but I don't know what to use to fill the question mark. I'm assuming I need
parameters since it seems doubtful the procedure is complete in itself (I'm
guessing a parameter is retention time and probably database?).
Thanks for the help.
Pete
these are output parameters.
declare @.num_genhistory_rows int , @.num_contents_rows int ,
@.num_tombstone_rows int
exec sp_mergemetadataretentioncleanup @.num_genhistory_rows output,
@.num_contents_rows output, @.num_tombstone_rows output
print @.num_genhistory_rows
print @.num_contents_rows
print @.num_tombstone_rows
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Pete" <Pete@.discussions.microsoft.com> wrote in message
news:C19A9C44-1298-4AC0-8088-57D4ED4DD799@.microsoft.com...
> I have a quick question that I could not find the answer for anywhere.
> The software developers that provided our SQL database program advised us
to
> put the subscription expiration on "never expire" because of their past
> experience with customers who do not maintain their databases. Because of
> this we now how massive meta data tables that need to be purged to
increase
> replkication performance (synchronization is extrmely slow). I have tried
> setting the subscription retention to 14 days, but the amount of data to
be
> purged is huge and it interferes with the synchroniztion over night.
> What I would like to do is use the stored procedure
> sp_mergemetadataretentioncleanup to individually clean up the meta data
> tables at each subscriber and the publisher. My problem is that I can not
> find the parameters and correct syntax for this procedure anywhere. I have
> seen the following:
> sp_mergemetadataretentioncleanup (?,?,?)
> but I don't know what to use to fill the question mark. I'm assuming I
need
> parameters since it seems doubtful the procedure is complete in itself
(I'm
> guessing a parameter is retention time and probably database?).
> Thanks for the help.
> Pete
The software developers that provided our SQL database program advised us to
put the subscription expiration on "never expire" because of their past
experience with customers who do not maintain their databases. Because of
this we now how massive meta data tables that need to be purged to increase
replkication performance (synchronization is extrmely slow). I have tried
setting the subscription retention to 14 days, but the amount of data to be
purged is huge and it interferes with the synchroniztion over night.
What I would like to do is use the stored procedure
sp_mergemetadataretentioncleanup to individually clean up the meta data
tables at each subscriber and the publisher. My problem is that I can not
find the parameters and correct syntax for this procedure anywhere. I have
seen the following:
sp_mergemetadataretentioncleanup (?,?,?)
but I don't know what to use to fill the question mark. I'm assuming I need
parameters since it seems doubtful the procedure is complete in itself (I'm
guessing a parameter is retention time and probably database?).
Thanks for the help.
Pete
these are output parameters.
declare @.num_genhistory_rows int , @.num_contents_rows int ,
@.num_tombstone_rows int
exec sp_mergemetadataretentioncleanup @.num_genhistory_rows output,
@.num_contents_rows output, @.num_tombstone_rows output
print @.num_genhistory_rows
print @.num_contents_rows
print @.num_tombstone_rows
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Pete" <Pete@.discussions.microsoft.com> wrote in message
news:C19A9C44-1298-4AC0-8088-57D4ED4DD799@.microsoft.com...
> I have a quick question that I could not find the answer for anywhere.
> The software developers that provided our SQL database program advised us
to
> put the subscription expiration on "never expire" because of their past
> experience with customers who do not maintain their databases. Because of
> this we now how massive meta data tables that need to be purged to
increase
> replkication performance (synchronization is extrmely slow). I have tried
> setting the subscription retention to 14 days, but the amount of data to
be
> purged is huge and it interferes with the synchroniztion over night.
> What I would like to do is use the stored procedure
> sp_mergemetadataretentioncleanup to individually clean up the meta data
> tables at each subscriber and the publisher. My problem is that I can not
> find the parameters and correct syntax for this procedure anywhere. I have
> seen the following:
> sp_mergemetadataretentioncleanup (?,?,?)
> but I don't know what to use to fill the question mark. I'm assuming I
need
> parameters since it seems doubtful the procedure is complete in itself
(I'm
> guessing a parameter is retention time and probably database?).
> Thanks for the help.
> Pete
Subscribe to:
Posts (Atom)