OWNET Database Structure

  • Hi,

    We need some help regarding with the explanation of the database structure (from OWNET). In the diagram we have all the tables and links, but when we try the perform a full description of the tasks vs front end we end in a dead streat... because, for example, where are the processes saved ? how is related a register and a process ? because we think that the info it's all spread all over the tables.

    Thanks,

  • I'm sorry, I don't understand what you're asking.

    Do you mean, where are the stored procedures? Depending on the app, there may not be any, but if there are, they're part of the database and you can see them from the Management Studio window.

    I did a quick search on OWNET. I see a lot of Python & Ingres stuff. Are you sure this is a SQL Server 2005 database?

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Hi, the OWNET Sw, it's mainly a Portuguese Document Management system with integrated workflow and our doubts is regarding with the questions that I've wroted before. Many thanks in advanced.

  • I still don't understand what you mean by tasks & processes. What those are and what you're attempting to compare between the database and the front-end?

    Do you mean the queries against the database? The stored procedures, etc.? You do have SQL Server Management Studio to connect to the database right?

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • If it's a third-party application... you really should talk to them about getting a data dictionary and/or whatever you wish from them. Some third-parties get very squirrely when you sniff too far into what they're doing - so I'd at least ask them for what they can give you, and/or let them know what you're up to. That way - you don't risk screwing up your relationship with them, and hopefully you don't run the risk of screwing up their code or processes by building something that competes with theirs.

    Messing with anything they built is likely a BAD idea, because it becomes a nightmare, and is usually the most efficient way to a. screw up your data, and b. get yourself "fired" as a customer of OWNET.

    I don't recall seeing your previous questions, so I am not quite sure your issues are.

    ----------------------------------------------------------------------------------
    Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?

  • Ok. I've think that you have wrote it's the best way to walk.

    Many tkanks.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply