Free Capitalist Network - Community Archive
Mises Community Archive
An online community for fans of Austrian economics and libertarianism, featuring forums, user blogs, and more.
Wikis » Ideas for Mises.org » Database Information

Database Information

Database Information

[Edit Tags]

A backup of the Mises database with confidential data stripped out  is available here:

Server: data.mises.org Username: miseshelp Password: miseshelp1

 

Complete DB Script of Mises DB:

6813.MisesDotOrgDbScript.zip

 

 

Priorities

  • TagGetRelatedTags - fix this to actually find related tags based on tags/metadata/content
  • Diagnose persistent hangs of Mises.org (I think it may be a locking issue)
    • Contact me if you need access to Sql Activity Monitor and/or Profiler
  • [DailyArticleGet] - NextId and PreviousId need to get the next and previous article.  (Doesn't work right currently)
  • Improve performance overall
  • Security audit to prevent sql injection for dynamically generated queries 
    • (mostly for media, documents, and articles)
  • MySql: we have a MySql instance on Windows 2003.  We need to automate backup in Windows Scheduler for it.
  • Delete old tables and sprocs
  • Is there anything not done that a DBA would do with our architecture?

Note: normally the database server is locked down by IP address whitelist.  Once we figure out who needs long-term access, I will solicit IP addresses and lock it down again.

Recent Comments

By: mpablazer Posted on Fri, Oct 16 2009 1:29 PM

I have been researching tag relevance literature over the past couple of days and there seem to only be several normally exploited methods by which tag relevance is determined.  The first method is basically what the proc does - measuring co-relatedness.  Another way is defining tag tuples for each combination of tags on a document and then measuring co-relatedness of the permutations of tag tuples (so basically a multiple level co-relatedness value).

I think the real value would come from the document metadata.  What metadata is available though on documents (or items - whatever they need to be called) and what tables are they stored in?

I will try some things starting with document data instead of a single tag passed in through the variable.

By: David V Posted on Fri, Oct 16 2009 5:35 PM

> Are the master, temp, and user DB's located on separate physical disks on separate physical controllers.  I have a transaction intensive DB that had substantial performance issues until I added a controller and disks and moved the user databases to it.  What is the physical layout of the MISESSATA2003 server?

It's a single server with 4 cores and a RAID 1 array.  Everything is on the same drive.  I think if we just optimized the worst queries, it would make a big difference.  I'm not a DBA.

By: David V Posted on Fri, Oct 16 2009 5:37 PM

>  The first method is basically what the proc does - measuring co-relatedness.

Yes but can we measure that by the number of tags that documents have in common?  Right now it just looks for any matching tag.

By: David V Posted on Sun, Oct 18 2009 8:18 PM

>  The first method is basically what the proc does - measuring co-relatedness.

Yes, I think this is what we need to do  better.

> Another way is defining tag tuples for each combination of tags on a document and then measuring co-relatedness of the permutations of tag tuples (so basically a multiple level co-relatedness value).

Can this be done on-demand, or does it require a scheduled task?

>What metadata is available though on documents (or items - whatever they need to be called) and what tables are they stored in?

Check out [dbo].[GetContentbyGUID]

We have all kinds of different documents - this is where I try to abstract out the schema.

By: David V Posted on Mon, Oct 19 2009 10:32 AM

Check out the "related stories" on this page"  http://mises.org/story/3766

View All