MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

MOSS 2007 SP2 issue? Custom SP's deleted?

  Asked By: Rachelle    Date: Apr 08    Category: MOSS    Views: 1073

We have a portal that was developed by a previous consultant using FBA.

Against all best practices, instead of using an external database for the FBA
data, he simply imported the ASP.Net provider tables and the SP's into the
SharePoint content database.

After applying SP2 the FBA errored out when you tried to sign in. Looking in the
SharePoint content database I noticed that ALL of the "aspnet_" stored
procedures are gone.

Does the SP2 delete and recreate all SP's in the SharePoint content database?



6 Answers Found

Answer #1    Answered By: Dominic Davis     Answered On: Apr 08

Microsoft owns the databases that it creates for SharePoint. I suspect that SP2
deletes ALL the stored procedures in the database and then re-applies them. The
fix is to create a new SQL database specifically for FBA, export the data from
the SharePoint content database and import it to those tables. Then change
your membership provider to point at the new database. It should not be in the
SharePoint database. Putting it there voids your service contract with

Answer #2    Answered By: Indu Raj     Answered On: Apr 08

Your consultant should have known better! Microsoft has a very fine line between
what will bring your SPS/WSS/MOSS environment into an unsupported configuration.

Answer #3    Answered By: Khushi Srivastava     Answered On: Apr 08

That would be true IF he was a SharePint consultant. Unfortunately, like 90% of
the time, he was just an ASP.Net guy that they gave SharePoint to and told him
to put up a site.

Answer #4    Answered By: Arti Patel     Answered On: Apr 08

Whether he knows SharePoint or not, I don't know of any product that Microsoft
sells where consultants are invited to make changes to the back end data store
provided by Microsoft. It's not a best practice in anything. I wouldn't even
do it with an in house developed product without verifying that it was OK first.
This is just bad design and an ASP.Net developer should know better.

Answer #5    Answered By: Claire May     Answered On: Apr 08

I thought as much. I pointed this out to them when I started, but they didn't
want to go through the pain of changing something that was working.

Now the problem is that a majority of the other sites used this same model when
FBA was needed.

Answer #6    Answered By: Dan Dickerson     Answered On: Apr 08

You're probably going to have to get a copy of the database restored
somewhere else and figure out what he put in the db, then add it back in.
Unless... he left you some *.sql scripts. Either way, at the end of the day,
Microsoft's not going to support your SharePoint configuration.

Didn't find what you were looking for? Find more on MOSS 2007 SP2 issue? Custom SP's deleted? Or get search suggestion and latest updates.