Table definition unknown
Moderators: chulett, rschirm, roy
Table definition unknown
Hello,
I have a problem with a table definition. I know only some columns of a table, I don't know if there are other columns besides the one I know. I can't get access to the database, because nobody knows the password, even if there is password on Administrator (but it is encrypted).
If I want to know if there are other columns on my table, how can I do? Is it possibile to make a select * from table? And what should I write in column names?
Thanks in advance-
I have a problem with a table definition. I know only some columns of a table, I don't know if there are other columns besides the one I know. I can't get access to the database, because nobody knows the password, even if there is password on Administrator (but it is encrypted).
If I want to know if there are other columns on my table, how can I do? Is it possibile to make a select * from table? And what should I write in column names?
Thanks in advance-
Re: Table definition unknown
That's your hurdle... without access to the database, everything else is moot. So, is this a database you "own"? If so, as DBA should be able to assign a new password.marco.mir wrote:I can't get access to the database, because nobody knows the password, even if there is password on Administrator (but it is encrypted).
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Copy the table to a dataset or to a table you create in a database you have got access to.
Use Runtime Column Propagation (needs to be enabled for the project in Administrator and on the Output-page of the DB-Stage).
Specify 'select * from tablename' as custom-SQL and leave the Schema-definition (Column-list) empty.
After that you can import the table-definition from the newly created dataset/db-table.
Use Runtime Column Propagation (needs to be enabled for the project in Administrator and on the Output-page of the DB-Stage).
Specify 'select * from tablename' as custom-SQL and leave the Schema-definition (Column-list) empty.
After that you can import the table-definition from the newly created dataset/db-table.
"It is not the lucky ones are grateful.
There are the grateful those are happy." Francis Bacon
There are the grateful those are happy." Francis Bacon
OK... so you have the password encrypted in the jobs but no-one locally knows what it is? Phil Hibbs has a utility that will (amongst other things) decrypt them, let me see if I can find it.
And no RCP in Server, I'm afraid.
Found it here: viewtopic.php?t=132851
And no RCP in Server, I'm afraid.
Found it here: viewtopic.php?t=132851
Last edited by chulett on Wed Oct 05, 2011 7:24 am, edited 1 time in total.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Re: Table definition unknown
I assumed what you are doing is legal. Otherwise the password should not be available as a project-variable, either.chulett wrote:So, is this a database you "own"? If so, as DBA should be able to assign a new password.
"It is not the lucky ones are grateful.
There are the grateful those are happy." Francis Bacon
There are the grateful those are happy." Francis Bacon
I don't see what could be considered "illegal" about it, never mind the fact that the password is encrypted. Usually the password in question is specific to the ETL functional user, so it's not like there would be far-reaching unknown consequences to having it reset. Hopefully.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 246
- Joined: Mon Jun 30, 2008 3:22 am
- Location: New York
- Contact:
BI-RMA wrote:Copy the table to a dataset or to a table you create in a database you have got access to.
Use Runtime Column Propagation (needs to be enabled for the project in Administrator and on the Output-page of the DB-Stage).
Specify 'select * from tablename' as custom-SQL and leave the Schema-definition (Column-list) empty.
After that you can import the table-definition from the newly created dataset/db-table.
Thank you! Your solution is good infact password is encrypted but I can use it as a parameter from Administrator, so even if I have to use server job, I can make a parallel job with that parameter to connect to the db and to use RCP (there isn't RCP in server jobs).