Environment
- Qlik Sense Enterprise on Windows
Transcript
Hello everyone, and welcome to another session of Q&A with Qlik. Today's topic is upgrading Qlik Sense Enterprise.
I'm going to introduce myself. My name is Emmanuel Herndon. I am one half of the co hosting team for this webinar.
I am a Digital Customer Success Specialist that works with customers from trial to renewal
in between and creating webinars like this one to enhance their journey.
Again, like I said, I'm not doing this alone. My colleague and co host, Troy, is doing this with me.
Will you say hello, Troy? Hi, everybody. My name is Troy Rainey. I work with Manny on this one and I largely
just help create helpful videos about Qlik, like this webinar.
But we've got an excellent panel of experts with you today. Let's let everybody go around and introduce themselves.
How about if we start with you, Alan? Hi, my name is Alan Slaughter.
I've been with Qlik for six years. So strictly dealing with Qlik Sense, and that's about it.
Great. Boris? Hi, my name is Boris Iwan. I've been working for five years and I'm a senior TAC on the EMA team.
Awesome. Thanks. How about you, Jay? Yeah, my name is Jay Brown.
I have been at Qlik for seven years and I am a subject matter expert on Qlik sense, infrastructure and connectivity.
I'm also a Signature Support Engineer. Thanks.
Mario? Hi, everyone. Great to be here again. My name is Mario Petre.
I am in the Signature Support team, along with Jay and several of my colleagues here today.
I'm celebrating eight years at Qlik this month and looking forward to another great panel today.
That's great. Congratulations. And, Mike. My name is Mike Dickson. I'm also part of the Signature Support team with Mario and Jay and Teams.
I've been with Qlik going on eight years in August, and primary focus has been Qlik Sense admin and deployment.
Excellent. All right, it's time to go ahead and submit those questions in the Q&A panel.
And we've already gotten a couple of comments. I'll read off the first one.
Qlik Sense version recommendation.
What version of Qlik sense do you recommend upgrading to?
Mario, you want to take that one? Yeah, I can take this one. So this is a flip flop question.
It has an easy answer and a slightly more complicated answer. The easy answer is, of course, always to the latest and greatest version
that we have available that will include the latest the latest feature releases. It will include all of the latest patches going up to that release.
But of course, depending on what deployment you have, how business critical this is, and how well it fits
in your overall deployment strategy, you can choose to go, let's say, N -1 and that would put you on
the latest release -1 to the latest that we have publicly available.
So in the case right now, we are on May 2023. As the latest publicly available,
an end minus one strategy would put you on the February 23 release. When using the strategy,
we always recommend to deploy the latest available patch on the download site to make sure that all cumulative bug fixes are included with your upgrade.
But that's essentially the gist of it. We always recommend you deploy the latest and greatest that will align you with
what we are trying to develop and put out there. But of course, depending on the size
of the deployment and again, how business critical this is, you can go for a more conservative approach and that would be N -1.
Troy is showing here the new download site that we have available where you can choose exactly which release you want to grab and it will show you
automatically all the patches available for that particular release.
Yeah, they're all available there. Great question to kick things off. Thank you.
Thank you. I have to do an upgrade for a customer who has currently has Qlik Sense installed February 2022.
Best way to upgrade Qlik Sense from February 2022 to February 2023.
Postgres SQL 96 and then Qlik is not installed on the C drive.
It says QA is a single node, product is a multi node.
I have problems with trying to upgrade to February 2023. What would be the best way to upgrade?
Anyone have any answers on that? Yeah, sure. This is Mike. I'll go ahead and work on that one.
If your Postgres SQL database is on 9.6, you are able to use
the Qlik Postgres Installer, which will update your database from 9.6
to 14.8. We do have an article on using that tool.
We also have a webinar that you can watch on using the tool. You'll want to go through this process
to upgrade off of 9.6 because it's no longer supported after November 2022.
After you upgrade your database, then you should be able to easily use the Qlik Installer to go through the motions of upgrading the environment
from February 2022 to the release that you're trying to go to.
If you run into issues during the upgrade, depending on the issue,
we might have articles out there already available for the upgrade process. But if it's a production environment and it goes down,
please submit a case with Qlik Support so that we can jump on a call with you as ASAP to help you get the install up and running right away.
But mainly the biggest thing you have to do is upgrade the database off of 9.6. As far as Qlik not being installed on the C drive, that shouldn't be a problem.
As long as the database, which is in the program data, Qlik Sense folder structure, as long as the database is still
in that location, then you'll be able to use the Qlik installer. As far as the program files of the exes of Qlik Sense being on a different drive,
that shouldn't be a problem and you won't run into any issues. To add a little bit here to Mike's feedback,
if you do happen to have moved your primary data location for the database itself, you need to make sure to move it back
in the original location before you attempt to upgrade with a Qlik Postgres installer, because it does expect the data to be in that original place.
Going forward, we should support custom locations as well. But for the time being, it does expect the database location to be under Program Data.
Some of our customers choose to symbolically point this to a different location.
Just keep in mind that you will have to essentially remove that symbolic link and bring the data back to the original location before you attempt to upgrade.
After that, you can move it back to the symbolic link target destination.
Yep, thank you. Thanks, guys. All right, moving on to the next question.
Importing Word document into Qlik Sense Cloud.
How to import personal Word document into Qlik sense Cloud? It's a little off topic, but anyone want to take that one?
I'm wondering what data this customer expects to extract from a Word document in Cloud.
It's not a typical data file. More in general, we do absolutely support the upload of all sorts of Office compatible data files,
including Excel files, CSV files, tab separated values, all sorts of data structures that Office applications can also open.
But the typical ones would be CSV and Excel files. Okay, thank you.
Next question says, There seems to be a lot of R&D focused on SaaS version.
Qlik Sense Client Management.
Is there a plan for enterprise to be a mirror of SaaS, or is it meant to lag behind to make us all switch to SaaS?
Little joke.
But if anybody has any comment. Yeah. So it doesn't sound like anyone on this call really has a great answer for this.
So let me just say that from what we're seeing in the field, most of the features that are available in SaaS do make their way to client managed.
They are usually related requests that are going on at the same time.
SaaS is treated as its own entity. The cloud team, people are working on that behind
the scenes, have a different focus than the client manage folks who may be working on something to make migration easier or to increase stability.
And those types of things, there's different priorities between those teams and what's going on.
So you will see that a lot of the cutting edge features and things like that will come to SaaS first.
And that's just because it's just easier to react in that space when a solution is
found, it can be deployed, and it can affect all customers. Whereas if you're trying to deploy a fix to client manage, then it usually affects
a specific version or a specific patch level. There's patch request and things for other
versions, older versions that might need to be branched off of that. It's just a little bit more slower moving in that aspect.
There's no intentional plan for enterprise to lag behind,
but you will see cutting edge features and the most up to date
deployments and patches and things making their way to SaaS first. Most of the delays with releases on such features on the Windows platform come
very simply from the release cadence that these products operate on. While we do continuous delivery on
Qlik Cloud services, for example, where we may deliver several new features during the same week, we only publish four major releases
containing possible new features for the Windows platform. So that might delay, essentially,
the arrival of these new features onto the Windows package itself.
Yeah, good point, Mario. All right, should I move on to the next one?
Instructions on upgrading to latest version of Qlik Sense.
There's a question here asking about the steps and version upgrades for someone
that's running Qlik Sense 2020 with Postgres SQL 9.6, and they want to move up to the latest version of Qlik sense.
What would be the path for that? I'll go ahead and take this. It's similar to the previous question as far as upgrading the database.
If you're on 9.6, that is no longer going to be supported after November 2022.
So you will want to upgrade the Postgres database to at minimum 12.5 or 14.8, which is if you want to use the tool.
If you would like to use the tool, you need to at least upgrade your Qlik Sense environment to February 2022 because that's where it's compatible.
If you would like to bypass stepping up to February 2022, upgrading the database,
and then upgradingQlik Sense again, you could create a backup of your
database, uninstall Qlik Sense, install the version that you would like to install, and then restore your database to the new version of Qlik sense.
So it's all preference on if you want to use the tools we have available or if you want to do it manually by doing
a backup and restore of your Qlik Sense environment. Okay, thank you.
Best way to avoid deprecated features issues.
Next question is, what's the best way to avoid issues with deprecated features?
Is there a step in installing, upgrading, or that will highlight these?
Anyone have notes? I would say the best way to... Yeah, sure. Go for it. The best way to do this is to review
the release notes to see what's been added to the product for its new features.
And you also can join the community blog, which would also update with any new issues to the product.
I'm just sharing where you can find those release notes on the community.
Yeah, support. This is easier. Release notes.
What was that other space you recommended? It's a blog that you can join.
Support updates blog. Yes. Then that will give you some updates on what's coming out, what's changing.
Definitely.
Great. Next question. Do patches need to be installed in order or can you jump to the latest patch?
Patches: installed in order version or jump to the latest patch?
This is a pretty simple question or a simple answer. It's just you do not need to step up. If you are on the initial release of a version and they say there's 14
patches for that version, you can go straight to patch 14. You do not need to step up individually to patch the environment.
These are all cumulative and the latest release notes attached to that, the very latest patch should also include
all of the list of included fixes up to that point. Listing exactly which patch they belong to so you can see exactly
where a particular issue was resolved, but they are cumulative. You also no longer...
This used to be a problem back in the day, but you no longer need to uninstall the old patch before you deploy a new one.
For those who remember those good old days or bad old days, depending.
Okay, thank you all for that. Next question.
It's a statement question, but here we go. We have issues with widgets getting
Post Upgrade Issues with widgets deprecation.
deprecated, which causes a lot of issues post upgrade.
Do any of you have an idea, maybe suggestion on how to... I'm assuming when we see widgets, we mean extensions
because those could definitely break in between major release jumps, especially if you are jumping multiple major releases in between upgrades.
But this is unfortunately the nature of third party extensions. These are maintained by third party
developers, and those developers in turn have to ensure that their extensions are compatible with the new versions of our
product, and also to make sure that they don't utilize potentially shifting the API calls, for example.
So we do tend to document very clearly in our API documentation, which a lot of these custom extensions
utilize to extend our functionality, whether these APIs are essentially
considered primitive and stable, or if they are bound to change. And of course, any either undocumented yet still public API endpoint
or those that are bound to change over time, if those are used in any particular extension and we change them
between releases, then that functionality may be affected. My advice would always be to contact
the developer of your custom extension first for support.
Great, thanks. Okay, the next question is around
Navigation guide document in the Qlik Sense cloud.
navigation guide document in the Qlik Sense Cloud. I guess how to find that?
We talked about that in the past and I'm wondering where we got that. There was a clarification question,
I believe, in the other chat mentioning that is it just possible to upload my user
navigation guide document into a Qlik Sense Cloud? I'm not entirely sure what this user means by that.
Just like a regular video or document to guide your users through the hub.
If that's so, of course, we have the original get started block that shows up
in the hub as you log in into your main console, and we have plenty of videos to
help guide you through those very early stages of using the cloud platform. But otherwise, I don't really know what this customer means by this.
Okay, we'll move on for now. But thank you for that.
Geo Analytics Plus Update with latest Qlik Sense EM installer
Next question, it says, Dear panel, geo analytics plus,
I guess they're asking, will it be upgraded with the latest click sense enterprise client manager installer, upgrade the installer?
That's a connector, and you will have to upgrade that separately to geo analytics plus connector.
If you're talking about the server package specifically, then same answer, really. These are two separate
products with their own installer, and they don't upgrade each other or to get them together, essentially, when you upgrade one.
For connectors, the latest version of Qlik Sense on Windows should include the latest version of our connectors for geoanalytics as well.
But if you're talking about the server components, those have to be updated separately.
Great. It is important to refer to the help for the geoanalytics. There's a Qlik Sense supported versions matrix out there that talks about what
versions of geoanalytics work with what versions of Qlik Sense. Just make sure that you refer to that before upgrading your products.
Moving on to the next question. I think asked to do with multi node deployments.
RIM nodes upgrades be notified if the Qlik Repository database service is not running?
Can upgrades for RIM nodes be notified if the Clique Repository database service is not running on the central node?
They've been caught by this issue before during upgrades where an upgrade on a RIM node might fail
towards the end of the process, leaving the server in an inconsistent state, and the virtual machine needs to be
restored in order to start the whole process from the beginning. So I guess in a multi node environment...
What will be the process in a multi node
deployment, we have lots of different rem nodes. Do you need to shut everything down at once? You do, but you need to make sure
that the database is available for communication during this installation process, which is why we always recommend that you
start with the central node upgrade to make sure that you have at least one node that is able to communicate with the database under the new version
so that they can orchestrate communication and setting of settings and certificates across the new machines as the new as the rem notes get upgraded as well.
The problem is that the check for communication with the database happens very deep into the installation process and is
asynchronous from the early steps in the wizard.
This doesn't actually prevent you from beginning the upgrade process itself.
But let's say the database can also happen to have crashed or be taken offline while the upgrade is in progress
on a given RIM node and that will also cause the same situation. This is excellent product feedback.
We'll make sure to take this to R&D for consideration. And of course, we also encourage our customers to use the ideation portal.
Yeah, I was totally thinking about that as well. This is an excellent opportunity to go to ideation here.
You can look at things that other people suggested, or you can make a suggestion.
Our product managers definitely review this content that gets uploaded here.
And when it comes time to add new features, this is the first place that they go.
So definitely take advantage of this feature on Qlik Community.
Thank you, Mario. Thank you, Troy. Next question we have that came in. On the download page, I believe I have access to all download
Access to files without a license; Data Catalog license
files, even for those we don't have license for. Is that accurate?
Is data catalog a separate license? Any ideas, anyone?
Yeah, you will have access to software that you don't have a license for, you can download it, but you won't be able to license it.
That is, and it is data catalog is a separate license. Just talk to your account manager if you have questions about it, and they can
get you squared away on how to obtain a license part of it.
And this is done really for convenience because not everyone that is typically downloading our installers every day will
have associated a license in our back end system. But still, as system administrators,
we want you to be able to download the software and install it, even if someone else will come after the fact with a license to activate it.
If this is not the same individual, at least the deployment process can get started.
And additionally, for the more perspicacious of you, you would have noticed that we
link to GitHub essentially for all of these releases. And those repositories can be followed and stored directly on GitHub to track our latest releases.
You don't necessarily need to go through the downloads page. The advantage of that is that it,
of course, gives us really good usage statistics about what our customers download and interact with on a regular basis.
But we get some of the same statistics from GitHub, I believe. And you can, of course, always go there directly for those.
Great. Next question. Should the service's account have a license or not?
Should the service's account have a license or not?
I've seen a lot of error log messages of various customers related to the service account on session counter
five might be related to the Qlik management apps.
So typically, the only reason you would the service account would need a license is if you're logging in to the Qlik
environment as a service account and consuming applications. Outside of that, the service account does
not need a license to fully work successfully. And you're correct on the monitoring apps is what typically is causing the session
count for the service account or the session count of five for the service
account because the monitoring apps does look... The data connections for the monitoring
app are using the service account and it does a connection onto that.
But if you don't have a license to that application for the service account, you won't see those errors.
But yeah, to answer your question, Shirley, the service account does not need a license.
The only ones who need the license is for users who are consuming applications via the hub.
And more in general, I think we're about to show another link that goes through the different scenarios
and how our proxy service interprets those in terms of session count. This will help you troubleshoot
instances of these errors in your logs and correlate with the type of usage that your users are generating on the platform or type of activity.
I can say from my own personal experience, when you do see a lot of occurrences of these types of errors,
it is often related to a badly integrated embedded object or application or sheet
in a third party platform for serving web content. This can occur in mashups as well.
There we go.
Yeah, this is that article, right? Because ultimately that service account is hitting
a rather primitive mechanism for preventing abuse on the platform,
and that is this max parallel sessions value of five, which cannot be changed
and has been part of the product since I believe version 1.0. All right, thank you.
Any Issue bypassing versions? Ex. Feb 22 to May 23
Next question, is there any issue bypassing versions of Qlik Sense, for example, going directly to May 2023 from February 2022?
Any thoughts? No, there is none. As long as you update first grade to 12.5, shouldn't be an issue.
Great. Indeed, I would be a little bit more cautious with larger jumps, especially coming from 2021 releases, as we have made some changes, for example,
to the properties contained in our self-sign certificates in between those and some other major changes to the product package itself.
But going anywhere from 22 releases to 23 release wouldn't be a problem.
All right. I love the next question. Is it safer to use the installer tool
Safer to use installer for Postgres upgrade 9.6 to 12?
for Postgres upgrade when moving from 9.6 to 12?
Well, this is my... If you're planning on using the installer
tool, it's going to be upgrading the database to 14.8, not 12.5.
But as regarding as it as regards to is it being safer or not,
I think it's going to be pretty safe to use. What's nice about it, it makes a backup of your database when using the tool.
It also renames the database folder to 9.6 deprecated.
Worst case scenario is that you could uninstall the standalone version
of Postgres SQL, rename the folder, and you haven't lost any data. You haven't had to do any type of restore, everything is still there.
So as far as safe, I think it's pretty safe to use, yes. But it will be upgrading your database to
14.8. We did have an older version of the tool which did upgrade it to 12.5,
but now it's upgrading to 14.8. 12.5 had recently some
security gaps identified as well, which is why we pushed with R&D to have our internal repository upgraded beyond that point.
I think it's a good thing. It also performs better overall.
I'm just showing an article with instructions for how to use that Postgres SQL installer and a link to a video where Mike demonstrates it.
And ultimately, for those more advanced admins out there, this is essentially a
convenience wrapper around the standalone installer from Postgres themselves. So if you know what you're doing, you don't have to use QPI to upgrade.
But of course, we do recommend all over the place during this article and other upgrade and restore articles, they always keep a separate backup of your
databases no matter what you do to the underlying system just so that you can recover in case of any mishap or disaster.
We do have this separate article on exactly how to do that quickly and easily.
All right, thank you. Next question actually has to do with Postgres and Installer.
Postgres installer Issue 14.8
They said, We have several problems with three customers now when upgrading from an older version.
We usually upgrade Postgres to February 2022 because of the version then goes to the desired version.
2022 works fine. Also, Postgres with Installer 14.8. However, when we when we then try
to upgrade to the desired version, it hangs on the Postgres installer.
First client could resolve it by a hard reset of the server while the freeze was
happening, but the others it didn't and got stuck at this step. Any tips on how this could be avoided?
Anyone have any ideas?
It sounds like they were able to eventually upgrade, but it just has gotten stuck at some point in the process.
I'd suggest you follow up with more specific errors or a little bit more in-depth description of exactly what
happens in the post where we describe how to use the QPI itself.
Several of us are monitoring that post actively and are in constant communication with R&D and the team that built the tool itself.
So we can take this particular scenario into consideration going forward. But I can't say I've seen this type of problem before.
And just for now, I would like to know more specifically exactly where this process gets stuck.
But for that, we would have to extract logs and whatnot, so it's better done offline.
Also, I would continue that. Make sure you do not have any third party scanning tools because that can interfere with your upgrade process.
Any type of malware scanning, antivirus scanning can interfere.
Okay. Next question, is there a recommended upgrade path for people running older versions?
is there a recommended upgrade path for people running older versions?
It's a bit of a follow up. For example, installations of Qilk sense that are older than February 2022?
Is there a stop that they should make until they get to the latest version?
Well, again, can you go back to the beginning of the question? What was the version they're jumping from?
Yeah, they're upgrading from an older version, for example, February 2022 is the example they gave, to the latest version.
That's not that old. That's really not that old. I would consider old anything that goes
beyond two years of the current latest release. There you might encounter some problem or hitch during the upgrade.
Most of them go very smoothly, but then we're also taking into consideration a whole lot
of environmental factors during these types of problems. There shouldn't be really an issue jumping
from, say, February 23, sorry, February 22 to May 23.
That's not that big of a jump in our books, at least.
Just going to post a link and another article with a step by step guide.
To continue the versioning question here, there is another question
that has to do with upgrading the operating system on these servers. This is a little bit trickier.
What to know when upgrading OS central node from Windows Server 12 to 19?
This particular user is asking, Anything to keep in mind when upgrading
the operating system? the central node from Windows Server 2012 R2 to 2019.
First, you're going to have to deal with the problems that may come up during the upgrade of the operating system
itself, and we can't really guarantee that that alone will go smoothly. Backups are your friend always.
And of course, having a full image of the central node server still on Server
2012 or whatever your original operating system may be, having an image of that server around in case of a disaster,
it is a great way to recover access and the platform for your users
while you figure out what went wrong during the upgrade. But of course, you have to take into account all of the core libraries that we rely on, such as
.Net, the communication stack that is very much newer in these more modern versions of Windows Server.
There's really a lot that could go wrong with the OS upgrade itself beyond Qlik working or not working.
Yeah, ciphers is something that we see a lot in the field when people upgrade the OS version.
A lot of that stuff changes, so you might see errors around TLS and things like that at the OS level.
What Mario said is correct. You definitely want to, if you can, send up another environment to test things out, migrate,
and make sure you have a good backup of your old environment just because at the OS level, it's difficult for a Qlik to assist with that.
That's really more of a client manage situation. Yeah.
And if this is a retirement issue where you need to retire this particular group
of servers because of how old the OS is or simply upgrade them in place, I would recommend essentially deploying new virtual machines.
If this is practical to you in this case, deploy fresh and start
from a fresh server that has a newer version of that operating system.
Instead of trying to operate something in place, your mileage may vary entirely. And starting with a clean slate is always
preferable, but not always practical, of course.
Okay, thank you for that. Next question has to do with migration of Qlik view from November 2017 to Qlik sense cloud.
Migrating from Qlik View from Nov ’17 to Qlik Sense Cloud
I think Troy has some information for us. But anybody else have an idea?
Yeah, I just saw that question come in. I forgot that I was sharing.
This was a textbook talk that I did with Jonathan Poole.
And we covered this very specific topic on helping people see a path on how you can upgrade your click view documents to click sense apps.
And we also talked a little bit around actually migrating to cloud in general,
but mostly we focused on moving your Qlik View documents, analytics documents, to Qlik Cloud analytics and what that path looks like.
And we explored lots of different tools that are available. There's some links down here to a Qlik View Converter tool,
migration tools, some best practices for visualizations, and all about moving from Qlik View to Qlik Sense.
So there's a lot of resources out there, including some packages from our professional services that will try and do a lot of the heavy lifting for you.
So there's definitely some paths out there. So I'll post this link into the chat and take a look.
Okay, the next question. I've done multiple Qlik Sense upgrades Postgres SQL going from 9.6 to 12.5 using
Avoid restoring all passwords for data connections after the upgrade.
the Strategy Backup database on install and restore the database.
Is there a way to avoid having to restore all passwords for data connections after the upgrade?
It's a good question. Yeah. So the only reason you would typically
need to restore all of the passwords for your data connections and or the user
director connector is if your certificates are changed. Our passwords are stored in the database and they're encrypted and they're
encrypted with the hash algorithm that are tied to the certificates. If your certificates in your environment during the upgrade do not change, then you won't need to restore or
reinter your passwords for all your data connections. If you use the Qlik Postgres SQL Installer, it just makes it back up.
It upgrades the database, installs a standalone version. It does not modify any of the certificates.
Typically, that's the only reason you would need to update the passwords is if your certificates have changed.
Make it back up for your certificates when you're making it back up for the environment so that you can do restore.
That's the best solution is to make it back up for your certificates and reimport those back in. I would say also if you're typically uninstalling the product
before an upgrade or choosing to install from scratch, make sure to leave the two options that have to do with local content disabled.
There is an option in there during the uninstallation progress that lets you tell the installer to also
remove your local database data along with the certificates on the machine.
If you leave that unchecked, the database center certificates will be left intact and when you upgrade,
those details will be reused by the new version installer.
Like Mike said, you're very likely removing your original certificate somehow
and recreating them during the installation of your new version, which is what's essentially invalidating all of these
encrypted values in your database as they can no longer be read with the old key.
So keep those around, like Mike said, and you should be fine. Next question we have, can multiple RAM nodes be updated at the same time?
Can multiple RAM nodes be updated at the same time?
Short answer, yes. Yes, they can. As long as you got the central node up and running and confirmed that everything
is working, your database is connected, all of your rem nodes can... If you run in a script to do the installs quietly or something to that extent on all
the different rem notes, yeah, that can be run simultaneously.
Great. We got a few more questions. I'm going to see if we can get through all of them.
Can you please recommend how to resolve the Postgres SQL vulnerabilities?
We've upgraded Postgres SQL from 9.6 to 12 and Qlik Sense from November 2022.
Our cyber security team reported Postgres SQL have multiple vulnerabilities. Can you please recommend how to resolve the Postgres SQL vulnerabilities?
That sounds very specific. I think we've talked about just touched it tangentally in a couple of previous answers,
but indeed there was a security vulnerability identified with 12.5. This is why we have pushed the QPI to support all the way up to 14.8. So use
the Qlik Postgres Installer to upgrade to a higher version or deploy one yourself, depending on how you installed the database to begin with.
And that should remove that security vulnerability. And of course, keep track of the CVE itself.
This is documented outside of our community as it affects Postgres directly.
Since I am talking about Postgres Resources, I'll take the next question as well asking about noticeable advantages running Postgres 14 over 12.5. We have
Noticeable advantages running Postgres 14 over 12.5.
noticed better stability overall since 12.5. Overall, I can't speak to any
specific improvements for Qlik operations directly just by using version 14.
But overall, if you want to consult what changed between these versions, you can always refer to the Postgres SQL
release notes that are available on their website. All right, thank you.
Roadmap on Qlik Sense version compatible with the newer DB version
Next question, when will there be a Qlik sense version that will be compatible only with the newer DB version?
An example, at least 12.5. Sure. November 2022 version of Qlik sense
is the first version that is requiring an upgrade off of 9.6. I believe our next
major version of August, we're going to start including 14.8, but it's not going to be required to upgrade to 14.8 for a while.
We're going to be supporting many different versions of Postgres SQL for a while.
But as far as what's installed with Qlik Sense, November 2022 is where we require something like 12.5. But until...
I think Mario could be wrong, but August is when we're going to release it.
The database is going to be 14.8 with the install of Qlik Sense, correct? Yes, that's the plan.
And by the way, to all practical effects, nothing really is going to happen if you are trying or attempting to start
the services on a much newer version of Qlik Sense, but pointing to an old version of the database,
but you will see a disclaimer in the QMC because this is essentially a self managed
resource, even if it comes deployed with Qlik Sense itself. But especially in the case of
you managing your own database server, you will have to own that part, essentially, and make sure that you upgrade accordingly.
But all that's going to happen is a disclaimer in the QMS team, as far as I'm aware.
It is possible that we will eventually drop backwards compatibility to 9.6 entirely.
But unless this happens, because we will, let's say, require a higher version of Postgres that is completely
incompatible with 9.6 or these prior versions. Our software should still support talking to the database.
That doesn't mean that it would be a supported deployment scenario by click support directly and click R&D.
But in a pinch, you should be able to get it to talk to that database in order to upgrade it further.
Postgres SQL password issue after upgrade Postgres Database
Great, thanks. All right, potentially the last question. When attempting to upgrade Postgres database using the QPI,
the installer tool, the installation stopped due to the password containing a forbidden character.
It advised we update the password. Is the best way to change the password to follow the documentation on how to reset forgotten Postgres SQL password?
We don't know the current password. Oh. We do know the current password is how I'm reading.
We do know the current password. That's right. Yeah. So the reason they're asking this in this way is because our password reset procedure assumes that you have forgotten.
Those steps involve putting the database into a temporary fully open state so that you can go in there as an admin user and run the queries required to set a new
password on whatever user ID you want to change it for.
But since you do have access to the database to begin with, all you need to do is run the alter part
of the command in our documentation to change the existing password. So you don't have to follow all
of the steps, but only the one that actually updates the new password.
And we can maybe point to the specific help. Yeah, I just put the article in the chat for Troy.
All right. Yeah, this is that article on how to change the... Yeah. So if you scroll down here...
There we go. A little bit further up, sorry. You skipped it.
A little bit right there. Okay, so these are the two queries that you would need to run with existing access to the database.
You can just go ahead and run these two queries and update those passwords. Just make sure you remember to update
the password in the relevant connection strings as well. If you're going to use that, if you're
going to continue to use that password, if you're going to change it back to the special character password, I don't think you have to update the connection strings after you run the QPI tool.
But it's probably a good idea just to remove those special characters and then go ahead and follow through with step two and so forth.
But you can definitely just give the initial steps to open up the database since you already have access to it.
Okay, well, I'm not seeing any further questions coming in.
So I want to thank everybody for joining today. We got a survey so you can send us some
feedback about the video today and the presentation. Hope everybody enjoyed it and we got their questions answered.
I want to thank our wonderful expert panels. Everybody, I appreciate all your
contributions and I hope everybody has a great rest of your day.