Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sassaidi
Starting Member
7 Posts |
Posted - 2002-07-18 : 09:34:39
|
| Hi,I need to know how I can mark a system stored procedure to a non-systemstored procedure. I have to edit it and put it back as a system storedprocedure.I know it is not recommended but I still want to do it for atest. The system stored procedure is called when a user logs in but Idon't know exactly when.Please help,S |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-07-18 : 09:53:32
|
Let me ask you this question:Are you really willing to take a chance on having you SQL Server blow up? Are you willing to risk losing data?I'm not saying this just because it's conventional wisdom:http://www.sqlteam.com/Forums/topic.asp?TOPIC_ID=12672And what he did there was FAR LESS risky than what you're proposing.As far as changing it, there is an sp_MS_marksystemobject procedure that is undocumented, however it only sets the system flag on, there's nothing that sets it off. And as indicated in Ken's Henderson's The Guru's Guide to SQL Server Stored Procedures, XML, and HTML:quote: Several functions and DBCC command verbs do not work properly unless executed from a system object
And unless you were part of the SQL Server development team you have no way of knowing which ones depend on the procedure you want to alter.My belabored point is this: you don't know what the consquences might be, and even if you're willing to take the risk, it's not something that you can rely upon to work 100% in a production environment. If you want to play with matches, go ahead, it's only your own house that will burn down.Sorry, but I can't give any advice other than this. DO NOT EDIT THE SYSTEM PROCEDURES. |
 |
|
|
|
|
|
|
|