Bill - if I am understanding your point correct...the table that changes is about 90 columns which contain anything and everything about our entities. The IDs do not change, but rather various information about the entities...for instance their home address, email, marriage status, etc.
We do...
Mufasa - I saw a slight improvement in the delete after running those lines of code. About 10 minute improvement on the overall procedure, and the delete takes the bulk of that.
Dagon - I will give your suggestion a try as well and post the results.
Thank you both so much for your help! This...
It varies, but here is a current approximation (from a test run today)
4071:272534
The table being deleted from is indexed, very well at that. But I also suspect that continuously doing these deletes/inserts on the large table (90 columns) may be wreaking havoc as well. But the only hang ups...
No, but it is simply a one column table with ids. The ids in the temp table drive the delete and insert.
So, would an index on this one column be the way to go?
We have table A which contains a great deal of information about our "entities" (id, name, address, etc.) in a specific format for the other system we send the information to and various reports, procedures etc. We can't change how this table is/the overall procedure is done because of the...
The counts do not match because we refresh the test database nightly and there is constantly changes being made to the entity and handling table from our users. We do many loads in the morning as well into production. But I did verify a select group of the entities which appear in the production...
I am logged in as the user who owns the tables, we only have one schema. This also happens with another select query, which is much simpler, so this tells me there has got to be something different between the two databases because the data is identical.
...Is there some sort of setting that may need to be changed?
Query:
SELECT e.ID_NUMBER
FROM ENTITY e
WHERE e.PERSON_OR_ORG = 'P'
AND EXISTS (SELECT *
FROM HANDLING
WHERE id_number = e.id_number
AND hnd_type_code = 'X'
AND hnd_status_code = 'A')
AND EXISTS (SELECT *
FROM HARRIS_DATA...
One of our Linux partitions is running into space issues and there are a couple databases on this partition that are not needed and would free up a significant amount of space.
Instead of blowing the db's away entirely, I'd like to somehow back them up (onto a different partition) just in case...
...table and I would like them to be a default value at all times.
Example:
CREATE TABLE test
AS
SELECT a.col1,
a.col2,
'999', <---**default value***
b.col1,
b.col2
FROM table1 a, table2 b...
I tried putting the line in like this and I error out:
colname varchar2(3) default...
Thanks for the reply...Well seeing I don't know a thing about macros it would be much appreciated if you would send me one, when you get the chance.
Thanks again,
Christina
Right now I am in testing mode on a updated test database (we are migrating from Costpoint 4.0 to 5.1). I have upgraded my Impromptu catalogs and placed them in a different directory (catalogs73). I attempted to use the report upgrade utility for all my impromptu reports, again they are in a...
This may be a long shot...but here goes...
I am using Impromptu 6.0
We have about 40 catalogs and over a thousand reports. Unfortunatly nothing was ever cleaned up for years and years but now I have to upgrade everything and I really want to clean up any unused reports/catalogs. It is a mess.
So...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.