April 3, 2008 at 2:42 am
In our database there is hundreds of system stored procedures that I don't know. A lot of them starts
with zzzzzzzz and we also have some sp_ procedures that I have no idea where are coming frome
I looked inside one of the procedures starting with zzzz and
it contained a call to
sp_MSrepl_PAL_rolecheck
Does anybody have any idea why these procedures are created, how to stop it, and
if it is safe to get rid of them?
Thanks 🙂
April 7, 2008 at 3:38 pm
In a regular replication setup, these stored procedures should not be there. Please check whether or not there was any other application, or the third party software, applied to your server.
April 7, 2008 at 8:41 pm
Um.... if it's not a 3rd party application, check the "Model" database... sp_MSrepl_PAL_rolecheck is a sproc from the Master database and shouldn't exist anywhere else.
Compare what's in the sp_MSrepl_PAL_rolecheck sproc you found and the one in Master... if they're different, either someone made a dreadful mistake, you bought a really whacko 3rd party sproc, or you've been hacked. Check each sproc that begins with sp_ and compare to what's in Master...
So far as the zzzzzz procs, I'd open a few up and see if there's a comment header for a 3rd party. If that fails, I get pretty nasty with things like those procs... if I don't know how they got there, I'll move them to a "holding" DB and see who/what breaks. Brutal, but very effective. Make sure management understands that you're going to do that before you do that... make them understand the possibility of a hack if nothing is reported as breakage.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2008 at 7:19 am
Ok, thanks for your replies. I will look more into this soon. It is pretty annoying with
all these strange proecdures
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply