Showing posts with label credential. Show all posts
Showing posts with label credential. Show all posts

Tuesday, March 27, 2012

Datasource credentials and linked reports

Hi,

we have a problem with linked reports. We are using the same reports that are run on about 70 different Oracle schemas. The credential information is passed when calling the report. This works fine for reports and reports with subreports. But when linking to another reports, the credential information is lost.

Is the a possibuility to pass the datasource credential information to a linked report?

Thanks in advance for your help

Michael

you could try setting up a credential parameter on the second report, and pass the credentials of the first report through to that report using the parameter...

Tuesday, February 14, 2012

database usage

I have an application which uses a special login credential (username and
password) to access several sql databases.
Its installed on several clients. what's the best possible way to determine
what all databases the application connected to, at the end of the day from
SQL Server Side. ?
thxskg,
You did not tell us which interface are you using to connect to sql server.
In case you are using ADO or ADO.NET, you can setup the property "Applicatio
n
Name" in the connection string. Then you will be able to use sp_who2 or
sysprocesses and look for that value.
AMB
"skg" wrote:

> I have an application which uses a special login credential (username and
> password) to access several sql databases.
> Its installed on several clients. what's the best possible way to determin
e
> what all databases the application connected to, at the end of the day fro
m
> SQL Server Side. ?
> thx
>
>|||Thanks!!. I am using ado.net. The clients can close the application at the
end of the day.
In that case i will not be able to find out, which database.
What iam looking for is whethere there is a record whether a user logged in
a particular database today?
"Alejandro Mesa" <AlejandroMesa@.discussions.microsoft.com> wrote in message
news:ED55575B-B66A-489A-8B3B-B2770446B696@.microsoft.com...
> skg,
> You did not tell us which interface are you using to connect to sql
> server.
> In case you are using ADO or ADO.NET, you can setup the property
> "Application
> Name" in the connection string. Then you will be able to use sp_who2 or
> sysprocesses and look for that value.
>
> AMB
> "skg" wrote:
>