Showing posts with label unable. Show all posts
Showing posts with label unable. Show all posts

Monday, March 26, 2012

hidden report parameters

Hi, my report has 3 parameters, 2 of which I don't want displayed since I
will set these programatically. I am unable to successfully make these
parameters hidden. I have tried the following suggested solutions:
1-) when parameter 'hidden' option is selected
error: "The given key was not present in the dictionary"
2-) when parameter 'prompt' option is selected with
prompt label set to empty
error: "The report parameter is read-only and cannot be
modified"
3-) when parameter 'prompt' option is selected with
prompt label set to one space.
no error, but parameters show up on report w/out labels.
4-) modify the RDL XML to leave an empty prompt
attribute - i.e. <prompt></prompt>
error: "The given key was not present in the dictionary"
I am running SQL 2005 June CTP. Reporting Services
version is 9.00.1187.00.
Thanks for any insight you can provide.
--steveEver discover problem. Some more information, we are trying to use RDL older
version and using in CTP2005 version and that is what is causing the error.
"stark" wrote:
> Hi, my report has 3 parameters, 2 of which I don't want displayed since I
> will set these programatically. I am unable to successfully make these
> parameters hidden. I have tried the following suggested solutions:
> 1-) when parameter 'hidden' option is selected
> error: "The given key was not present in the dictionary"
> 2-) when parameter 'prompt' option is selected with
> prompt label set to empty
> error: "The report parameter is read-only and cannot be
> modified"
> 3-) when parameter 'prompt' option is selected with
> prompt label set to one space.
> no error, but parameters show up on report w/out labels.
> 4-) modify the RDL XML to leave an empty prompt
> attribute - i.e. <prompt></prompt>
> error: "The given key was not present in the dictionary"
> I am running SQL 2005 June CTP. Reporting Services
> version is 9.00.1187.00.
> Thanks for any insight you can provide.
> --steve
>sql

Friday, March 23, 2012

hi,Re: Unable to get SQLCMD utility to work properly.

I try to go to a command prompt to get this to run right with no luck. Is there something that I am not doing right? It gives me the help library, but thats about it. Also, I have dealt with Oracle in the past. And was wondering is there a way to access the SQLCMD utility on a workstation with a login of some kind?

--David

hi David,

SqlCMD accepts a list of parameters as described in http://msdn2.microsoft.com/en-us/library/ms165702.aspx and at http://msdn2.microsoft.com/en-us/library/ms170207.aspx you can find a tutorial about it's use...

usually you open a command prompt window and provide the appropriate connection parameters, like

c:\Document and settings\user>sqlcmd -E -S.\SQLExpress

this tries a trusted connection to the local SQLExpress named instance...

if you got it succesfully you get a prompt like
1>

qhere you can just type your Transact-SQL statements..

regards

Friday, March 9, 2012

HelpSQL Agent Security

We have sensitive data that requires the builtin\administrators group be removed so domain admins are unable to see data. When we do this, SQL can continue to run under the local system account, but the SQL Agent cannot.

Does anyone else have a solution that will lockout NT admins (both local and domain) and allow both SQL and the SQL AGENT to run properly?

TIA

Ryan HuntDid you give the new domain account sysadmin rights?

And configure it to start with that account?|||Thanks for the response. I ended up just creating a local admin account for the agent with specific SA rights to the server. Then, had the only department allowed to have access to the data change the password. This seems like the best choice...

Thanks