If your concern is that some of the sprocs did not execute properly you could just run the sql to create/alter the procs again under Host Settings - SQL.  Check the run as script option.  Or you could use Query Analyzer or some such tool.

---

Shawn Duggan MCPD
BlueTango Software - Canada Web Content Management
Website Design | DotNetNuke Hosting | DotNetNuke Tips and Tricks Blog
AuthIntegrator - The Easy Way To Integrate DNN and ASP.NET Applications
KeepAlive - Why Should Your Site Be Slow?

Most of the problem is outlined This thread

Primarily, When I try to install a module (hosts/upload new module) whether it is a upgrade or a new module, I get lots of errors - some process is running SQL queries with the database user name set as the objectqualifier for the table sysobjects.  sysobjects should always be referred to as "dbo.sysobjects", but I keep getting errors where it is referred to as "empulse_dnnuser.sysobjects".  Apparantly that was a problem with earlier versions of DNN that has supposedly been fixed.  I have looked through all the stored procedures and all the dataprovider files looking for a place where the sysobjects table is referenced with the databaseowner as the objectqualifier, but haven't been able to track the culprit down. 

I think that my host may not have had the permissions for the ASP.NET worker process set properly when I made the initial upgrade from 3.2.2 to 3.3.5 and that may have  prevented some processes from installing porperly.  At least that is my current working theory.   I wanted to try a complete reinstall, hopefully preserving my current data.