• Hi Kim!

    Hi Kim!

    I asked this one a while back:

    https://www.docuware.com/forum/english-forums/docuware-questions-about-usage-and-configuration/searching-system-fields-web-client

    Basically, you add a field to the file cabinet that exposes the system fields beneath, and then you can decide what dialogs to display those new fields on.

    Hope this helps!

     

    Thanks,

    Joe Kaufman

  • Thanks!

    Thanks, Phil!

    Where can I find the various compatibility lists between versions of DocuWare and SQL Server, IIS, Windows Server, etc. I assume all of those dependencies are lain out somewhere.

    I will look into getting us updated to 2016!

     

    Thanks,

    Joe Kaufman

  • Follow up...

    Hey all,

    Does anyone have any thoughts or "gotchas" about this? Any documentation I may have missed on upgrading the database behind DocuWare?

     

    Thanks,

    Joe Kaufman

  • Upgrade SQL Server? Gotchas?

    Hey all,

    A third-party CMMS system is offering to send us a MS SQl Server BAK file containing the full system database, daily, so we can mount it on our SQL Server and have all data locally for our own reporting, etc.

    Problem is, they are backing up from SQL Server 2014 and our SQL Server is 2012. This server is the database upon which our on=premise DocuWare system resides.

    We are on DW 6.11 with all hotfixes installed. Can we simply upgrade SQL Server from 2012 to 2014 without issue? I am assuming so, just wanted to make sure.

    For that matter, should we just go all the way to SQL Server 2016? Will that work OK for DocuWare 6.11? we do not have the resources to try all this on a test server and test every single file cabinet and task manager setup. If all goes haywire, we would simply restore the entire DocuWare server image (which includes SQL Server) from backup (the server is virtualized). Apolgies if there is a upported database listing somewhere that I missed (I did search the forum but couldn't find anything quite specific to our scenario).

    Let me know any gotchas with upgrading SQL Server behind DocuWare, and any downside to just going all the way to SQL Server 2016. We might as well, assuming it doesn't have any obviously pitfalls.

     

    Thanks,

    Joe Kaufman

  • Gilles,

    Gilles,

    That makes complete sense -- a "whole word" sort of motifier. Though, in 6.11 if I search for "ant" I got 22 documents highlighting the word "QUANTITY". If I threw asterisks on either side of "ant" I got over 200 hits, also finding the word "ATTRACTANT". I am not sure I understand why a straight "ant" found inside QUANTITY would not also be found in ATTRACTANT. A "contains" should be a contains whether a search term is found at the start, middle, or end of a word.

    Definitely differing results, though!

    The "?" makes complete sense, though -- that is a good example you offer.

     

    Thanks,

    Joe Kaufman

  • Giles,

    Giles,

    That is weird if they changed that -- but might I ask why you would need a wildcard like "*" in full-text search? Isn't full-text searching inherently a "contains" situation (i.e. a term with wildcards on both sides, *<term>*)? To put it another way, I cannot imagine a search term with an asterisk returning anything other than what is found for the base search term?

    Not sure about "?" -- does something like a Google search generate different results based on positional wildcards? I'm off to test!

     

    Thanks,

    Joe Kaufman

  • Larry,

    Larry,

    Glad you figured it out! Welcome to the powerful world of SQL!  *smile*

     

    Thanks,

    Joe Kaufman

  • Query

    Larry,

    I assume you are using MySQL Workbench? I do not have an example of accessing DocuWare with that, since our database is MS SQL Server. But the methodology is the same.

    Assuming you are connected, you need to go to the correct database, or "schema" as MySQL calls them. I have attached a picture of accessing a MySQL database I have set up to store weather data from my personal weather station at home, just to give a feel for how the databases are listed.

    I have also attached what a DocuWare database listing looks like in SQL Server. AS you can see, file cabinet data is in a database/scheme called "dwdata". Expand that database and find the table representing the file cabinet. It should have a similar name, though certain characters are converted to underscores and the name will be in all capital letters.

    Once you have the table visible, right-click on it and choose "Select Rows" from the menu. This will generate a query to return all rows in the table, such as:

    SELECT * FROM <schema name>.<table name>;

    If you just want the count of records, you can use this for your query:

    SELECT COUNT(*) AS NumRecs FROM <schema name>.<table name>;

    That will just return the singleton field denoting th enumber of records in the table, and that should be your number of documents in the file cabinet.

    Hope this helps!

    Thanks,
    Joe Kaufman

    https://www.docuware.com/sites/default/files/forums-images/dw_mysql.png

    https://www.docuware.com/sites/default/files/forums-images/dw_mssql.png

  • Just do a SQL query

    Larry,

    Can you access the SQL Server under the data and see how many documetns are in the cabinet? That's the easiest way to count at this point... This must be on-premise, right? You can download SQL Server Management Studio and access the SQL Server database directly (or MySQL explorer, if that is the db), and then do a quick select query.

     

    Thanks,

    Joe Kaufman

  • Bernie,

    Bernie,

    Did you even try rebooting the server entirely? And that still didn't bring the link back?

    Yes, you can have multiple links. They display down the side of the viewer, and can each point to their own criteria and result list.  That is, if you can make them appear.  *smile*

     

    Thanks,

    Joe Kaufman