badly need help

Question

Post reply

badly need help

Teemo

Ten Centuries

Points: 1376
More actions
November 29, 2010 at 5:55 pm

#97535

Hi community,
badly need help on this one, Im using SQL server 2000 and my first problem is that, how can I modify the sys.objects table? and my 2nd problem is that, how will i decrypt a WITH ENCRYPTION stored procedure in SQL Server 2000?
and one more thing, if i modify the sys.tables, is there any logs or trace for that kind of changes, and if there is, where can i find it? and is it possible to delete permanently?
Thanks

Viewing 15 posts - 1 through 15 (of 30 total)

You must be logged in to reply to this topic. Login to reply

SQLRNNR SSC Guru Points: 281334 More actions · Answer 1

sys.tables and sys.objects are SQL 2005 and above.

For SQL 2000, they are sysobjects and systables. I recommend not altering any of the MS Shipped schemas.

There are also many methods for decrypting SQL 2000 stored procs - many of which can be found by googling for that very thing.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

Teemo Ten Centuries Points: 1376 More actions · Answer 2

thanks for the reply

Im sorry i use the sql 2005 keyword, the changes that i want to made is in sql server 2000, i google it and many said i can do that using DAC with single user mode, but still i cant understand how to do it, and regarding the enryption, all i found on the web is that i need to buy a seperate software to decrypt the encrypted stored proc. as much as possible i want to do it using sql server.

Lowell SSC Guru Points: 323518 More actions · Answer 3

InfiniteError (11/29/2010)
thanks for the reply
Im sorry i use the sql 2005 keyword, the changes that i want to made is in sql server 2000, i google it and many said i can do that using DAC with single user mode, but still i cant understand how to do it, and regarding the enryption, all i found on the web is that i need to buy a seperate software to decrypt the encrypted stored proc. as much as possible i want to do it using sql server.

the much more important question is:

what do you need to do that you think you need to edit the system tables directly?

with the ultra rare exception of trying to fix corruption, anything you think you need to do has a proper, recommended way to do it instead.

since you think you need to decrypt something, i'm guessing you need to find or change someones password...no need to edit system tables to do that.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Teemo Ten Centuries Points: 1376 More actions · Answer 4

thanks for the responce,

honeslty, the exact thing that i want to do is to modify the date modifed column for a

stored procedure, and regarding the encryption, all i want is to check the t-sql codes of that stored procedure without using any third party software.

Lowell SSC Guru Points: 323518 More actions · Answer 5

InfiniteError (11/29/2010)
thanks for the responce,
honeslty, the exact thing that i want to do is to modify the date modifed column for a
stored procedure, and regarding the encryption, all i want is to check the t-sql codes of that stored procedure without using any third party software.

i think this will work:

change the servers date.

alter the procedure, change the date back.

google for sql 2000 decrypt procedures.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

WayneS SSC Guru Points: 95460 More actions · Answer 6

Lowell (11/29/2010)
InfiniteError (11/29/2010)
thanks for the reply
Im sorry i use the sql 2005 keyword, the changes that i want to made is in sql server 2000, i google it and many said i can do that using DAC with single user mode, but still i cant understand how to do it, and regarding the enryption, all i found on the web is that i need to buy a seperate software to decrypt the encrypted stored proc. as much as possible i want to do it using sql server.
the much more important question is:
what do you need to do that you think you need to edit the system tables directly?
with the ultra rare exception of trying to fix corruption, anything you think you need to do has a proper, recommended way to do it instead.

The most likely effect of directly modifying the system tables is to... cause corruption. 😀

Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes

If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!

Links:
For better assistance in answering your questions
Performance Problems
Common date/time routines
Understanding and Using APPLY Part 1 & Part 2

Teemo Ten Centuries Points: 1376 More actions · Answer 7

i tried that, but unfortunately it did not work... is there any other way..?

Teemo Ten Centuries Points: 1376 More actions · Answer 8

The most likely effect of directly modifying the system tables is to... cause corruption. 😀

i just need to modify the date modified column, that's all, and nothing else if i cant modify that, there will be a big trouble and it's to personal to say it here...

WayneS SSC Guru Points: 95460 More actions · Answer 9

InfiniteError (11/29/2010)
i tried that, but unfortunately it did not work... is there any other way..?

Actually, altering the procedure does not change the create date... you have to drop the procedure, then create it again.

Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes

If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!

Links:
For better assistance in answering your questions
Performance Problems
Common date/time routines
Understanding and Using APPLY Part 1 & Part 2

WayneS SSC Guru Points: 95460 More actions · Answer 10

InfiniteError (11/29/2010)
The most likely effect of directly modifying the system tables is to... cause corruption. 😀
i just need to modify the date modified column, that's all, and nothing else if i cant modify that, there will be a big trouble and it's to personal to say it here...

Whoops, date modified, not date created. If changing the computers' date didn't do it, then you probably need to change the computers' date, and then restart the services.

If it's on a domain - do you have a time server pushing the time out? If so, try taking the server off the network first.

Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes

If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!

Links:
For better assistance in answering your questions
Performance Problems
Common date/time routines
Understanding and Using APPLY Part 1 & Part 2

Teemo Ten Centuries Points: 1376 More actions · Answer 11

Whoops, date modified, not date created. If changing the computers' date didn't do it, then you probably need to change the computers' date, and then restart the services.
If it's on a domain - do you have a time server pushing the time out? If so, try taking the server off the network first.

thank you again for the responce, ok i will try that one and give you a feedback if it's successful or not, because what i tried so far is to change the computer date/time "forward" like for ex. 1month ahead, and it did change the date modified column when i alter the procedure, but when i change the date/time of the computer backward like for ex. 1 month before, it did not change the date modified column.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 12

Do not even consider touching the system tables. They are not there for you to edit. There's a reason that 'allow updates' was disabled on SQL 2005+.

if i cant modify that, there will be a big trouble and it's to personal to say it here...

Now why would you want to change the modify date for a procedure? Maybe because you changed the proc in production when you shouldn't have and now want to cover your tracks?

If that's the case, there's a slight ethical problem there. If you did something that you shouldn't have done, go and own up for it. It'll likely come out eventually and if you're caught covering up it'll be far worse trouble.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

SQLRNNR SSC Guru Points: 281334 More actions · Answer 13

I am curious why you would need to modify the date field in this way. It seems like there is some covering of a mistake going on. Please explain to us why this change may be needed.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

SQLRNNR SSC Guru Points: 281334 More actions · Answer 14

GilaMonster (11/29/2010)
Do not even consider touching the system tables. They are not there for you to edit. There's a reason that 'allow updates' doesn't work on SQL 2005+. Also note that sys.objects is not even a table.
if i cant modify that, there will be a big trouble and it's to personal to say it here...
Now why would you want to change the modify date for a procedure? Maybe because you changed the proc in production when you shouldn't have and now want to cover your tracks?
If that's the case, there's a slight ethical problem there. Technical one too, changes of procedure are logged into the default trace and anyone monitoring that will know what you did.
If you did something that you shouldn't have done, go and own up for it. It'll likely come out eventually and if you're caught covering up it'll be far worse trouble.

I wish I would have seen this prior to my posting. This is really well said.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events