we all know that Oracle doesn't recommend creating custom objects in those sacred accounts (like sys, system, etc...)
I would never create a table but package or procedure seems to be safe enough to me...
Could someone explain me why ?
Printable View
we all know that Oracle doesn't recommend creating custom objects in those sacred accounts (like sys, system, etc...)
I would never create a table but package or procedure seems to be safe enough to me...
Could someone explain me why ?
Because Oracle says not to -- good enough for me.
Oracle suggests not to do so, 'cause the tablespace would get fragmented due to the user objects which in turn will affect the performance of the database.
-Chintzs
*cough* bullsht *cough*
:)
Chintz,
I agree with you about tables but package won't cause any fragmentation....
what do you think about packages,and other pl-sql under sys, system, etc...?
Sounds to me like someone made an "ooops" and is trying to it cover up.Quote:
Originally posted by lanna
Chintz,
I agree with you about tables but package won't cause any fragmentation....
what do you think about packages,and other pl-sql under sys, system, etc...?
OracleDoc,
"Oops" is not done yet. But i'm planning to do it. So far I don't see any reasonable answers on my question and "because I said so" is not good enough for me
Then I suggest you go for it and learn the hard way.Quote:
Originally posted by lanna
OracleDoc,
"Oops" is not done yet. But i'm planning to do it. So far I don't see any reasonable answers on my question and "because I said so" is not good enough for me
40000 People working at Oracle say not to do that and you say otherwise, start your own revolution I guess. Why not write a White paper on How I learned to stop worrying and create objects Willy Nilly in the system tablespace?Quote:
Originally posted by lanna
OracleDoc,
"Oops" is not done yet. But i'm planning to do it. So far I don't see any reasonable answers on my question and "because I said so" is not good enough for me
Well.. dont think in perspective of DB/DB Performace/Blah.. Blah..Quote:
Originally posted by lanna
OracleDoc,
"Oops" is not done yet. But i'm planning to do it. So far I don't see any reasonable answers on my question and "because I said so" is not good enough for me
But think at an application point of view and also manageability.. then you will get your answers..
Abhay.
PL-SQL and system tablespace - ???:confused:Quote:
Originally posted by stmontgo
40000 People working at Oracle say not to do that and you say otherwise, start your own revolution I guess. Why not write a White paper on How I learned to stop worrying and create objects Willy Nilly in the system tablespace?
Then dude by all means knock yourself out! While you're at it don't forget to analyze the sys and system schema to make sure those packages get picked up.Quote:
Originally posted by lanna
OracleDoc,
"Oops" is not done yet. But i'm planning to do it. So far I don't see any reasonable answers on my question and "because I said so" is not good enough for me
leave it be dapi,jeff,dave
Thank you for your reply Abhay,Quote:
Originally posted by abhaysk
Well.. dont think in perspective of DB/DB Performace/Blah.. Blah..
But think at an application point of view and also manageability.. then you will get your answers..
Abhay.
so you think except for manageability there is no other fallbacks?
So what is the advantage of creating them under the SYS or SYSTEM schema then?
You might like to think about the joys of exporting anbd importing user-created objects in the SYS/SYSTEM schema also.
Funny you can't find some more interesting "oops" to do.
Why no deleting a datafile, dropping some objects...etc..Staff like that you know. Just to make sure you can recover to a point in time in the past.
In case of...
Quote:
Originally posted by yanban
Funny you can't find some more interesting "oops" to do.
Why no deleting a datafile, dropping some objects...etc..Staff like that you know. Just to make sure you can recover to a point in time in the past.
In case of...
Funny how people are trying their best to insult others. Usually if they have nothing smart to say they "bite" back....
oh, well, i'm disappointed in this forum and low intelligence level of most of the members.
Actually I wasn’t planning to create any pl-sql in sys or system but In other predefined schemas. But I wanted to throw sys/system in to see the worse case scenario. Looks like intelligent conversation is beyond this forum.
don't bother to reply on this one
You got no intelligent discussion because it is an idiodic idea. Putting objects into pre-defined schemas is a great way to void any support agreement. Putting objects into pre-defined schemas is a great way to confuse the crap out of everybody using the database. I could think of over 100 reasons why not to do it, but the number one reason is common sense tells me not to.
Read the damn book dude or dudette and don't bother to reply to this one eitherQuote:
Originally posted by lanna
Funny how people are trying their best to insult others. Usually if they have nothing smart to say they "bite" back....
oh, well, i'm disappointed in this forum and low intelligence level of most of the members.
Actually I wasn’t planning to create any pl-sql in sys or system but In other predefined schemas. But I wanted to throw sys/system in to see the worse case scenario. Looks like intelligent conversation is beyond this forum.
don't bother to reply on this one
Guys one suggestion.. If you think original poster posted some nonsense Qz.. than dont reply.. why do you wana abuse..
By not repying he will know his/her Q was either
1) too tough to answer..
2) too stupid Q to be answered..
--
--
--
Well now dont ask me why am I replying now ;)
Abhay.
...or every hour they'll ping their thread and say "Any Updates?". Frankly, I'm surprised this wasn't URGENT!!!