Comments on: SAS SPM 2.x and the mysterious sas_wdetemptable http://blog.saasinct.com/2009/10/21/sas-spm-2-x-and-the-mysterious-sas_wdetemptable/?utm_source=rss&utm_medium=rss&utm_campaign=sas-spm-2-x-and-the-mysterious-sas_wdetemptable :: Sharing with the world everything we discover about SAS. Wed, 14 Jul 2010 17:49:08 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Shane Gibson http://blog.saasinct.com/2009/10/21/sas-spm-2-x-and-the-mysterious-sas_wdetemptable/comment-page-1/#comment-518 Shane Gibson Thu, 05 Nov 2009 08:56:21 +0000 http://blog.sasinct.com/?p=184#comment-518 Did some more testing and this table isnt used when submitting the calc from within the SPM administrator web page. So im guessing it only gets used when you use the projcalc function via code. Will test that when I get a chance. Also the records get inserted into the table and then deleted once the calc is completed so you wlil need to watch it via mysql admin during the calc. Did some more testing and this table isnt used when submitting the calc from within the SPM administrator web page.

So im guessing it only gets used when you use the projcalc function via code. Will test that when I get a chance.

Also the records get inserted into the table and then deleted once the calc is completed so you wlil need to watch it via mysql admin during the calc.

]]> By: sasfrog http://blog.saasinct.com/2009/10/21/sas-spm-2-x-and-the-mysterious-sas_wdetemptable/comment-page-1/#comment-457 sasfrog Thu, 22 Oct 2009 06:07:26 +0000 http://blog.sasinct.com/?p=184#comment-457 OK, just a quick update: I looked at our wdetemptable and it had 1790 observations. [Mysteriously, many of the values for "last modified date" were prior to the date we first installed (indeed, even purchased) SPM.] I then ran a Calculate for a period that encompasses all the data we have in the main project on site... now there are (wait for it) 1790 observations in there. The same ones, I'd reckon. I haven't had time to explore & profile the records in there (and probably won't until the alleged 'quiet time' around Christmas) - possibly, they're not from the main project for which I did the Calculate. Maybe we could go offline from this blog to to- and fro- on this one, and post any major insights. Cheers Shane sasfrog OK, just a quick update:

I looked at our wdetemptable and it had 1790 observations. [Mysteriously, many of the values for "last modified date" were prior to the date we first installed (indeed, even purchased) SPM.]

I then ran a Calculate for a period that encompasses all the data we have in the main project on site… now there are (wait for it) 1790 observations in there. The same ones, I’d reckon.

I haven’t had time to explore & profile the records in there (and probably won’t until the alleged ‘quiet time’ around Christmas) – possibly, they’re not from the main project for which I did the Calculate.

Maybe we could go offline from this blog to to- and fro- on this one, and post any major insights.

Cheers Shane

sasfrog

]]> By: Shane Gibson http://blog.saasinct.com/2009/10/21/sas-spm-2-x-and-the-mysterious-sas_wdetemptable/comment-page-1/#comment-455 Shane Gibson Thu, 22 Oct 2009 05:26:49 +0000 http://blog.sasinct.com/?p=184#comment-455 I agree I always thought this table was only for Web Data Entry as well, which we don't use, and that is also what SAS Tech Support said. I am still investigating this to see if we are doing something weird, because as you would expect we want the calc's to be as fast as possible and the Mysql database to be as un-fragmented as possible given it current size. Having said that I am always amazed at how fast the SPM Portlets are returning values given the size of our projects. I don't know if the calc's after the DI Studio loads did this either, because I never bothered to look at what was happening. Let me know if you find anything and ill post any updates I find as well. Cheers Shane I agree I always thought this table was only for Web Data Entry as well, which we don’t use, and that is also what SAS Tech Support said.

I am still investigating this to see if we are doing something weird, because as you would expect we want the calc’s to be as fast as possible and the Mysql database to be as un-fragmented as possible given it current size. Having said that I am always amazed at how fast the SPM Portlets are returning values given the size of our projects.

I don’t know if the calc’s after the DI Studio loads did this either, because I never bothered to look at what was happening.

Let me know if you find anything and ill post any updates I find as well.

Cheers
Shane

]]> By: sasfrog http://blog.saasinct.com/2009/10/21/sas-spm-2-x-and-the-mysterious-sas_wdetemptable/comment-page-1/#comment-447 sasfrog Wed, 21 Oct 2009 09:37:33 +0000 http://blog.sasinct.com/?p=184#comment-447 Hi there I (for reasons I can't recall) thought the "wde" stood for "web data entry", and that this was the table that stores any metrics that have been captured through web data entry forms, if the project-level option to eyeball before "publishing" wde-captured data is checked. Since we never used the (rather clunky) web data entry forms, I never really got a chance to check this assumption. It hadn't occurred to me that it might be involved in calculating a project. I'm inspired to check our sas_wdetemptable contents next time I'm looking at the back end, and do some of my own sleuthing on this. BMF loads shouldn't touch this table (but nor should DI load jobs have done). How are/were most of your 10K records being added each week? I'm keen for you to keep this post updated as you learn more! Cheers sasfrog Hi there

I (for reasons I can’t recall) thought the “wde” stood for “web data entry”, and that this was the table that stores any metrics that have been captured through web data entry forms, if the project-level option to eyeball before “publishing” wde-captured data is checked.

Since we never used the (rather clunky) web data entry forms, I never really got a chance to check this assumption. It hadn’t occurred to me that it might be involved in calculating a project. I’m inspired to check our sas_wdetemptable contents next time I’m looking at the back end, and do some of my own sleuthing on this.

BMF loads shouldn’t touch this table (but nor should DI load jobs have done). How are/were most of your 10K records being added each week?

I’m keen for you to keep this post updated as you learn more!

Cheers
sasfrog

]]>