Connectivity to Informix Database

I am evaluating MS SQL Server Reporting Services and during the process, I
encountered issues pertaining to connectivity with Informix Database.
I want to design a report by retrieving data from Informix
database. I have a code that generates the .RDL file (which is in XML
format). When I deploy the .RDL file on the server, it does so successfully.
But when I try to view it through the IE 6.0 its gives me an error -
An attempt has been made to use a data extension '****' that is not
registered for this report server. (rsDataExtensionNotFound)
How could I solve this problem ?
Hi
The account that is running the Reporting Server Service, does it have
permission to access the Informix database?
Is the Informix driver installed on the server? Have you checked
connectivity from the Web Server to the DB?
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Skeptic45" <Skeptic45@.discussions.microsoft.com> wrote in message
news:AD68D8B3-0B49-488F-B09A-D41D129E6344@.microsoft.com...
> I am evaluating MS SQL Server Reporting Services and during the process, I
> encountered issues pertaining to connectivity with Informix Database.
> I want to design a report by retrieving data from Informix
> database. I have a code that generates the .RDL file (which is in XML
> format). When I deploy the .RDL file on the server, it does so
> successfully.
> But when I try to view it through the IE 6.0 its gives me an error -
> An attempt has been made to use a data extension '****' that is not
> registered for this report server. (rsDataExtensionNotFound)
> How could I solve this problem ?
>

connections

im writing a service that will be on a app server
this is one of many service's to process Recordsets from Sql Server...
1 service may have 20 Processes to Complete
example
main class PreProcess()
method CleanNames();
method updateNames();
methodr ValidateContracts();
Various things must be completed
Suedo Example below
My question is
in the main class make my connection and keep it for all sub members
or connect in each member
A. This Way opens connection...closes connect

method cleanNames()
1 get connection
2 get recordset
3. Close Connection
4 process Recordset
5. Open Connection
4 Commit Changes
6. Close Connection()
finished cleanames()
or
method cleanNames()
1 get connection
2 get recordset
3 process Recordset
4 Commit Changes
5. Close Connection()
finished cleanames()
or
this final way is in the parent Class or Calling Function
sends in the connections holds it open till the service is
completed of all jobs its Suppose to do
then releases the connection

method cleanNames(oconn) connection as parameter
1 get recordset
2 process Recordset
3 Commit Changes
finished cleanames()

Thanks
DavePDaveP (dvs_bis@.sbcglobal.net) writes:

Quote:

Originally Posted by

im writing a service that will be on a app server
this is one of many service's to process Recordsets from Sql Server...
1 service may have 20 Processes to Complete
example
main class PreProcess()
method CleanNames();
method updateNames();
methodr ValidateContracts();
Various things must be completed
Suedo Example below
My question is
in the main class make my connection and keep it for all sub members
or connect in each member

I'm not really sure I understand, but if the members are intended to
be separate threads, you should definitely have one connection per
member.

If they are just different tasks that a single-threaded service will
perform, it's more of a toss-up, but I think the idiom today is to stick
with local connections. Keep in mind that ADO .Net maintains a connection
pool where it lingers to disconnected connections and then reuse them
if there is a request for a connect with the same properties within
some timefram (60 seconds, I believe).

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Connection to MySql in SSIS

I have a process that copies data from a MySql database to Sql Server. This process has worked fine on another server but is failing on a new server. I created an ODBC connection to the MySql database which works fine. In the job, it has a Connection Manager object to the MySql database which Tests successfully. The job has a Datareader source with a very simple SQL command in it. When I run the job, I get the following error:

Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning.

Error: 0xC0047062 at Data Flow Task, DataReader Source [1]: System.Data.Odbc.OdbcException: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction)

at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction)

at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction)

Error: 0xC0047017 at Data Flow Task, DTS.Pipeline: component "DataReader Source" (1) failed validation and returned error code 0x80131937.

Error: 0xC004700C at Data Flow Task, DTS.Pipeline: One or more component failed validation.

Error: 0xC0024107 at Data Flow Task: There were errors during task validation.

It says that the Data Source Name Not Found. If this was so, how is the connection manager test succeeding?

I am running the MySql driver version 3.51.12.

Any ideas what might be causing this to fail will be greatly appreciated!

Are you using expressions or configurations on the connect string?

Connection still apperas in SQLServer Entreprise Manager over Locks / process ID

Hello,
i have a doubt here, after a close the connection, i still can see the last stored procedure active in the LOCKS/PROCESSID in enterprise manager of SQL SERVER.
I think i'm closing the connection well

Try

IfMe.ID > 0Then

Dim strSqlAsString = "SP_CHANGECLASSCONTENTS"

Dim sqlcommandAsNew SqlCommand(strSql,New SqlConnection(ConnStr))

sqlcommand.CommandType = CommandType.StoredProcedure

sqlcommand.Parameters.Add("@.PerformActivation", SqlDbType.Bit).Value = 0

sqlcommand.Parameters.Add("@.PerformInactivation", SqlDbType.Bit).Value = 0

sqlcommand.Parameters.Add("@.PerformDelete", SqlDbType.Bit).Value = 1

sqlcommand.Parameters.Add("@.PerformUndelete", SqlDbType.Bit).Value = 0

sqlcommand.Parameters.Add("@.PermanentDelete", SqlDbType.Bit).Value = CBit(PermanentDelete)

sqlcommand.Parameters.Add("@.Class_ID", SqlDbType.Int).Value = _id

sqlcommand.Connection.Open()

sqlcommand.ExecuteNonQuery()

sqlcommand.Connection.Close()

Else

Err.Raise(10205, "CLASS", "CLASS ID is empty")

EndIf

Catch exAs Exception

_err = ex.Message

Return Err.Number

EndTry

Hi,

.NET Framework SQl data provider utilizes database connection pooling (there's one pool per unique connection string). When you close a SqlConnection, it is returned to this pool (there are min amount of connections in the pool ) and the hard connection to the db is not necessarily closed (connection ).
E.g this way usage of connections is kept efficient and opening & closing of "real connections" is kept minimum.
Here's more details
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconconnectionpoolingforsqlservernetdataprovider.asp

|||ok tks,
but what if i use many procedures like this one several times, and each one creates it's own connection. Even if i close the connection well it still appears several processes concerning this procedures in SQLSERVER. does this degrades the performance ?
tks|||

Hi,
see the previous link for exact details.
Anyways, it happens within the limits of the connection pool. If there are free connections in the pool, they are utilized to fullfill those which you instantiate and run e.g even if you instantiate new connections in code, the pool might be able to deal with them without increasing its size (the actual pooled connections are of type SqlInternalConnection not those which SqlConnection objects which you instantiate).
If the pool cannot deal with new connection requests, it starts creating new ones (within the max limit of the pool). If max limit is reached then new connection requests are queued. Note also that after a burst usage of connections, they are also dropped from the pool to the mimum limit when lifetime has expired or connectiion is severed.

E.g the pools are there to keep connection count in control in situation like these.