Hi all,
With our report/response database, fault_no's can have one, multiple or
null response_no's. The SQL below returns distinct fault_no's regardless
if it has one, multiple or null response's. The SQL does the job, but
can you figure out it uses up a large amount of CPU (60% on an Ultra
Generally speaking, getting a spike above 60% is nothing to worry about. How
long does the processor stay above 60%? If it is for several seconds, then
you might have something to think about.
First, how is your table indexed? I would hope as a minimum you have an
index on the Fault_No and
- Stacy Mader [EMAIL PROTECTED] on 07/29/01 23:03:10 +1000:
With our report/response database, fault_no's can have one, multiple or
null response_no's. The SQL below returns distinct fault_no's regardless
if it has one, multiple or null response's. The SQL does the job, but
can you figure
What is the smallest, simplest SQL-like database supported by DBI?
After several winding attempts to answer this through web searching,
I came across several postings where a NoSQL-DBI driver was mentioned,
but with no further context, and neither NoSQL nor the DBI site have
any information ---
Steve,
Thanks for the info. The view was created using the fault_no column as the common
link between my two original tables.
Using your idea of the GROUP BY clause, I created another view
(report_response_index)
which contains only the fault_no and latest response_no. Created like:
CREATE
Dear Dbi-Users,
I have a number of MS Access databases (30+) that all have the same
structure. I would like to configure my DSN so that it points to each of
these databases in turn, I can then extract the information I want.
Does anyone know if this is possible? I don't really want to
Then use a dsnless connection. Look at perldoc DBD::ODBC for the examples
(connecting to Access) that are already listed.
--Neil
-Original Message-
From: Michael Blackmore [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 30, 2001 10:51 AM
To: [EMAIL PROTECTED]
Subject: DBI::ODBC
the way I understand it, the whole point in having a DSN is to have a
permanent definition of a database connection so that it does not have to be
programmatically created. I don't believe that, in Perl, anyway, there is a
way to actually change the attributes of a DSN. (I'm assuming you are
Dear All,
This code snippet shows the solution:
The only trick is that you need to double escape the directories if you
specify them in a string.
...
my $dbfile = v:mdbsperlmdb.mdb;
my $dsn = driver=Microsoft Access Driver (*.mdb);dbq=$dbfile;
my $dbh = DBI-connect(dbi:ODBC:$dsn) or
right, but... not to be difficult or anything, but that's not really a
dsn... it is a connection string. A dsn is an ODBC data source name (on
windows) which is configured through the control panel. But yes, this would
be the solution to the question.
(btw you could probably use a single quote in
10 matches
Mail list logo
