While working on checking the Stored Procedures for blietzkrieg (or however it's written) package I noticed that many of them will not run due to wrong column names being used or more weird scenarios.
I have basically gone through each one of the errors and manually fixed the references so that stuff like SMC doesn't crash like crazy on you anymore.
The fixed Stored Procedures seem to be related with automatic content creation which could be related to a tool we don't have access to by Joymax. But some of them have to do with Stall Network (the ItemQuotation creation Stored Procedure is messed up by default, and I'm not 100% sure that my version will fix any ItemQuotation issues if any).
How to use this?
Open your SQL Management Studio, open a Query after selecting your SRO_VT_SHARD, and place the text in the attached file inside. Run the query with F5 and see how your Stored Procedures get reapplied with no errors.
How can I know if my Stored Procedures are screwed?
Do this if you do not want to run my queries with blindfold and want to know if your database has issues by yourself. Follow these steps to reproduce the way that I found that the SPs were screwed:
- Enter your SQL Management Studio.
- Right click on your SRO_VT_SHARD (or equivalent).
- Select Tasks/Generate Scripts.
- Click on 'Next' or 'Choose Objects' in the sidebar.
- Select 'Select specific database objects'.
- Mark the 'Stored Procedures' checkbox and hit Next.
- Click on 'Advanced' and change the 'Script DROP and CREATE' option to 'Script DROP and CREATE' instead of 'Script CREATE'.
- Click on 'Next' twice to generate the scripts with your Stored Procedures.
- Go to your 'Documents' and open 'script.sql' with Miscrosoft SQL Management Studio.
- Select SRO_VT_SHARD and run the query.
- Check any errors in the output to verify if your SPs are clean or not.
- Fix any errors and keep running the query until everything in your output is black.
Are my other databases good or not?
I just thought about checking the other databases, but I'm too lazy to do it right now. Might go ahead and do it later on, but anyone else is welcome to reproduce the steps above to check their other databases.
I recommend you to check your Stored Procedures manually if you are a capable developer, since I am not the smartest one out there. This could come with new bugs that nobody ever saw before, so take care with my releases jeje.






