Data migration STAR via KB_SQL

[John L]

Hi gang, I've recently been assigned the task of archiving a single hospital region on STAR that has KB_SQL installed and I have pretty basic questions though I'm very good with financial components and SQL extractions. Is KB_SQL pretty much the same language as SQL server? I can't seem to find a lot of documentation on line. I'm trying to prep myself before our kick off call. Any recommendations??

Thanks.

Johnny.
Djjse...@gmail.com

[The Marquee]

Hi John,

KB_SQL is a modified version of SQL meant to deal with MUMPS, which is a nosql database with features of relational databases.  KB_SQL is designed to handle MUMPS globals.  From what I've seen, there seems to be a huge overlap between KB_SQL and SQL, but I'm not advanced at either and can't tell you where they break down.  If you're just looking for what you can used based on prior knowledge of its standard variant, I think most will  likely be applicable directly.  Hope that helps!

Thank you,

Mark

--
You received this message because you are subscribed to the Google Groups "hisnet" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hisnet+un...@googlegroups.com.
To post to this group, send email to his...@googlegroups.com.
Visit this group at https://groups.google.com/group/hisnet.
For more options, visit https://groups.google.com/d/optout.

[Kimberly Core]

If you know T-SQL you'll have a good base for KB_SQL, although there's some definite differences and things to know.

Knowledge Based Systems has a website with a tech support section that has all kinds of information about KB_SQL syntax. (https://www.kbsystems.com/kbsql.html)

KB_SQL can't do union queries like T-SQL can, but there's a lot I like better about KB_SQL - just in the BREAK and DETAIL sections alone. The GROUP BY, BREAK AT/BREAK AFTER, DETAIL statements will be good places to start.

KB_SQL allows you to write a nicely formatted report in sections etc. without having to use something like SSRS to write a report after you have a SELECT query.
I learned KB_SQL before I learned T-SQL, so it’s possible I'm a little biased towards KB_SQL ;)

There may still be a bunch of us still around that can help with syntax questions. The biggest hurdle if you're not familiar with the STAR database will be choosing the *right* place to get data.

If you’re looking for formal training there's folks out there that do that as well - probably some of us could dig up contacts for you if needed.

Feel free to email or call me directly, I've been writing KB_SQL queries for 19+ years. There are probably still folks around that can help you with both syntax and data questions.

Regards,
Kim

Kimberly Core | Systems Analyst | Transform Shared Service Organization | (519) 352-6401 x6971 | Kimber...@transformsso.ca



CONFIDENTIALITY STATEMENT:  This email transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the email address.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this email is strictly prohibited.  If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system.
Please ~ only print this email if necessary!  Reduce, Reuse, Recycle!

[Kimberly Core]

I should clarify that the version we're on didn't do UNION queries but I think that's not true in later versions.

[John L]

Thank you all for your help, especially the KB link. This is also my first Google site so forgive me while I get accustomed to the formatting. 

For my migration project, from the STAR application I'll only be doing (I'd gather select) statements since I'm not editing data that's already in there.

TY Kim!

-J

[Sherwin Ditlove]

Kimberly

In addition to regular KB_SQL, I consider it "character based", is the product that I have used is QRE.  If it's available, it makes coding alot easier.

Sherwin Ditlove

Consultant, retired

[Kimberly Core]

Yes, QRE can be very helpful, especially if you need to do any sort of copy/paste.  Using KB_SQL inside of STAR Vista Reporting is as you say character based.

I use both regularly, depends what I’m doing.   A big benefit of QRE is the colour coding, that visible clue you’ve got it right (or wrong)

 

Kimberly Core | Systems Analyst | Transform Shared Service Organization | (519) 352-6401 x6971 | Kimber...@transformsso.ca

 

 

CONFIDENTIALITY STATEMENT:  This email transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the email address.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this email is strictly prohibited.  If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system.

P Please ~ only print this email if necessary!  Reduce, Reuse, Recycle!

 

From: his...@googlegroups.com <his...@googlegroups.com> On Behalf Of Sherwin Ditlove
Sent: Thursday, April 11, 2019 4:20 PM
To: his...@googlegroups.com
Subject: Re: Data migration STAR via KB_SQL

 

Kimberly

 

In addition to regular KB_SQL, I consider it "character based", is the product that I have used is QRE.  If it's available, it makes coding alot easier.

 

Sherwin Ditlove

Consultant, retired

 

On Wed, Apr 10, 2019, 2:29 PM John L <djjse...@gmail.com> wrote:

Thank you all for your help, especially the KB link. This is also my first Google site so forgive me while I get accustomed to the formatting. 

 

For my migration project, from the STAR application I'll only be doing (I'd gather select) statements since I'm not editing data that's already in there.

 

TY Kim!

-J

On Wed, Apr 10, 2019 at 2:08 PM Kimberly Core <Kimber...@transformsso.ca> wrote:

I should clarify that the version we're on didn't do UNION queries but I think that's not true in later versions. 

Kimberly Core | Systems Analyst | Transform Shared Service Organization | (519) 352-6401 x6971 | Kimber...@transformsso.ca



CONFIDENTIALITY STATEMENT:  This email transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the email address.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this email is strictly prohibited.  If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system.

P Please ~ only print this email if necessary!  Reduce, Reuse, Recycle!

-----Original Message-----
From: Kimberly Core
Sent: Wednesday, April 10, 2019 2:05 PM
To: hisnet <his...@googlegroups.com>
Subject: RE: Data migration STAR via KB_SQL

If you know T-SQL you'll have a good base for KB_SQL, although there's some definite differences and things to know.

Knowledge Based Systems has a website with a tech support section that has all kinds of information about KB_SQL syntax.  (https://www.kbsystems.com/kbsql.html)

KB_SQL can't do union queries like T-SQL can, but there's a lot I like better about KB_SQL - just in the BREAK and DETAIL sections alone.  The GROUP BY, BREAK AT/BREAK AFTER, DETAIL statements will be good places to start.   

KB_SQL allows you to write a nicely formatted report in sections etc. without having to use something like SSRS to write a report after you have a SELECT query. 
I learned KB_SQL before I learned T-SQL, so it’s possible I'm a little biased towards KB_SQL ;)

There may still be a bunch of us still around that can help with syntax questions.  The biggest hurdle if you're not familiar with the STAR database will be choosing the *right* place to get data.

If you’re looking for formal training there's folks out there that do that as well - probably some of us could dig up contacts for you if needed.

Feel free to email or call me directly, I've been writing KB_SQL queries for 19+ years.  There are probably still folks around that can help you with both syntax and data questions.

Regards,
Kim

Kimberly Core | Systems Analyst | Transform Shared Service Organization | (519) 352-6401 x6971 | Kimber...@transformsso.ca



CONFIDENTIALITY STATEMENT:  This email transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the email address.  If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this email is strictly prohibited.  If you are not the intended recipient, please notify the sender immediately by return email and delete this message and any attachments from your system.

P Please ~ only print this email if necessary!  Reduce, Reuse, Recycle!

[guerra...@gmail.com]

Hey Friends,

I have work in data extraction projects with Sherwin excellent resource for data migrations using QRE.

:)

Miguel Guerra

[John L]

I've worked with a ton of different EHRs in my career, but not STAR, so I'm thinking that there will be be a system administrator to walk me through the basic screens when we have the kick off cal in order to define the specs (list of data elements that they want extracted). I do know T-SQL fairly well, though I'm always in learning and have to pull up my on line MS cheat sheets from time to time. LOL. 

[SW2]

Allscripts offers a robust STAR Archive Solution that is available from their sales team.  Looks like they get the important data from the system and provide user interfaces to that data once migrated.  According to sales team several customers live on solution along with site references available.  Nobody knows the STAR Database better than the Vista Team, might be worth investigating.

 

Attached is a sales document that was provided to me.

[John L]

Hi all,

I know I started this discussed a few weeks ago, but in 2 weeks or so we're gearing for a kick off call. Would I be correct in my assumption that I would be taking their .BAK file and restoring it locally in order to start looking at the data elements? Does that sound like a  sound strategy?

Thanks,

John

[guerra...@gmail.com]

There is not *.bak file as in MSSQL. 

To view this discussion on the web visit https://groups.google.com/d/msgid/hisnet/CANpF6r%3DRRD3c38pESqd-CLHde4zbDi5wNzov0WCM9YWT0YsyqQ%40mail.gmail.com.