Showing posts with label creating. Show all posts
Showing posts with label creating. Show all posts

Friday, March 30, 2012

Peduliar problem in SSRS

Hi all ,

I am encountering a peculiar problem while creating a linked report in SSRS.

The scenario:

My first reports contains 3 columns . The first 3 columns contain data from vendor table in AdventureWorks DB. They are VendorID , Name, CreditRating. The fourth column contains a link to the second report. It is just a link which jumps to the other report and passes the above three values as parameters to the second report.

The second report contains 4 parameters which includes VendorID , Name, CreditRating and one more Postedby parameter which has to be entered manually when the second report is displayed. The three parameters from first report are passed on and one extra parameter has to entered manually then only the second report displays.

It works fine when I check it on Visual Studio preview mode. I click the link for a particular row in First Report and it asks me to enter the Postedby Parameter. After entering it it displays the 2nd report. But the problem arises when I deploy it to report server. When I click the link on first report it throughs an error like " The Parameter 'PostedBy' is missing a value" whereas it should prompt the user to enter the PostedBy Parameter.

I am stuck in this and not able to understand why this happens in ReportServer and not in Visual Studio Preview mode.

Does anybody has any idea why this is happening ?

Any Suggestion will be appreciated.

Regards...

Girija Shankar Beuria

You must specify the default value for the fourth parameter. Visual Studio is an interactive environment, so you get to enter the value on request by the VS. But in production environment, reports are consumed by other applications and the report will not be able to request for an input from the calling application and this applies to Report Manager also which is an external web application that consumes the reporting services.

Shyam

|||

just go to the code and see if there is any parameter hard coded in xml.

Remove that parameter and save it .

This will probably solve your problem.

Vamsi Krishna Korasiga

Monday, March 12, 2012

password sql 2005

I am creating an db login called test to test some sripts. When I try to set
that password it says password validation failed. The password does not meet
windows policy requirenments because it is too short.
In sql 2005 is the password policy based on your windwows policy?
stoney wrote:
> I am creating an db login called test to test some sripts. When I try to set
> that password it says password validation failed. The password does not meet
> windows policy requirenments because it is too short.
> In sql 2005 is the password policy based on your windwows policy?
>
It can be, but doesn't HAVE to be. Study the options that are available
when you create a new login.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||I think that this is the behvior if the OS is windows 2003. In any
case you can use the option CHECK_POLICY = OFF when you create the
login. Here is an example:
CREATE LOGIN MyLogin WITH PASSWORD = 'MyPass', CHECK_POLICY = OFF
Adi
stoney wrote:
> I am creating an db login called test to test some sripts. When I try to set
> that password it says password validation failed. The password does not meet
> windows policy requirenments because it is too short.
> In sql 2005 is the password policy based on your windwows policy?

password sql 2005

I am creating an db login called test to test some sripts. When I try to se
t
that password it says password validation failed. The password does not mee
t
windows policy requirenments because it is too short.
In sql 2005 is the password policy based on your windwows policy?stoney wrote:
> I am creating an db login called test to test some sripts. When I try to
set
> that password it says password validation failed. The password does not m
eet
> windows policy requirenments because it is too short.
> In sql 2005 is the password policy based on your windwows policy?
>
It can be, but doesn't HAVE to be. Study the options that are available
when you create a new login.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I think that this is the behvior if the OS is windows 2003. In any
case you can use the option CHECK_POLICY = OFF when you create the
login. Here is an example:
CREATE LOGIN MyLogin WITH PASSWORD = 'MyPass', CHECK_POLICY = OFF
Adi
stoney wrote:
> I am creating an db login called test to test some sripts. When I try to
set
> that password it says password validation failed. The password does not m
eet
> windows policy requirenments because it is too short.
> In sql 2005 is the password policy based on your windwows policy?

Friday, March 9, 2012

Password Protected Excel File

Hi

I'm in need of a bit of assitance here. Basically I am currently creating a SSIS package which works in principle with the exception of my data flow.

On my data flow I am reading an excel file using the excel source, this works fine for a number of my examples but one of the excel files is password protected. This is throwing an error when I try to run the package.

Does anyone know how to read a password protected excel file?

Thanks
Kismet123You cannot access a password-protected Excel file using the Jet OLE DB Provider, period.

I probably shouldn't mention this, but as an interesting tidbit of useless knowledge, the Provider can access the file if it is open at the same time in the Excel application...and without even providing the password. But doing so causes a huge memory leak in the Excel process that's going to bring things down sooner or later.
Q319998 BUG: Memory Leak When You Query Open Excel Worksheet with ADO
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q319998

-Doug
|||Thanks for that information Doug. Could you possibly tell me what the Password property is referring to when you create an Excel Connection Manager. I thought it would have something to do with if the connection you are making is password protected.

Kismet

Monday, February 20, 2012

Passing SQL Clauses as Parameters to a Stored Procedure

Hi,

I have a complex SQL query against multiple tables that ideally would be best used as a stored procedure.

I know of and have read about creating named parameters and setting the parameters' values in ASP just before issuing an execute command via the Command object. What I'd like to do is assign the text of the filter and sort clauses to the parameters. Not the values, but the entire string, such as

"WHERE lastname LIKE 'A%' "

"ORDER BY lastname "

I need to assign the entire clause because the query may or may not use a particular clause.

I have experimented. However SQL treats the parameter as a literal string rather than part of the SQL query itself. Is there another technique that I may use to accomplish my goal?

Thanks in advance for your opinion, suggestion, criticism, etc.

--Tom.Dynamic SQL|||and look up SQL Injection

DECLARE @.SQL varchar(8000)

SELECT @.SQL = 'SELECT * FROM INFORMATION_SCHEMA'
EXEC(@.SQL)

You should use dynamic as a last reort...

What prob you trying to solve?