I've recently migrated my Ektron installation (8.01 SP1) to a new server which had the regional settings as US (ran the installers, moved database and restored).
I changed the region to UK and restored the database (a backup from a server which was region UK).
However when a user selects a date (say publication date metadata) using the date picker , it's displayed as UK but saved in US format.
What configuration change do I need to do to fix this?
I've fixed the issue. I looked at which users were running the Ektron services (local user) and SQL Express (Network services).
I then applied the UK regional settings to the system accounts by following these instructions
http://windows.microsoft.com/en-gb/windows-vista/apply-regional-and-language-settings-to-reserved-accounts
Did a reboot and the dates are in the correct format.
Related
I have a web solution with about 1000 clients. Nowadays they have access to reports that I provide as a PDF: an ASP.NET script executes SP's in the database and with PDFReactor I create a PDF. This is online and as you may already be guessing, it is unmanageable for large data sets.
I was thinking of using a reporting solution, as Power BI, Tableau or... Qlik. In my investigations I have found out that Qlik is the most complete solution for what I want. Nevertheless, I still have some questions, regarding the application architecture and how I can integrate Qlik with my application.
The first question is how I manage my users? I have a custom authentication provider and user management inside my application... What is the best way to integrate with Qlik? I manually configure all the clients in the Qlik Server also? There are endpoints to do it automatically?
The second question is how I manage what a client can see inside a Qlik document (QVW). I want to have several unique QVD, where several QVW get their data from. But I don't want to create a QVW for each client!! Can I filter a QVW based on a user authentication?
I would like that my clients could see the reports dynamically inside my web app. But my conclusion so far is that the web view of Qlik is static and that for more dynamism my users would have to use Qlik View desktop. Correct?
And this leads me to the final question: does my clients would have to pay licenses or is everything on my side and responsibility?
Thanks for your help!
Regards,
David
Out of the box QlikView Server (see 4.2) uses NTFS authentication (local windows users or Active Directory). There is something called DMS - ticket based authentication which allow non Windows users to be authorized to access apps. A bit more info here
QlikView have something called Section Access which is on file (qvw) level. Section Access is part of the QV script. Basically you can create link between user name and data field. The main file will contain all the data but when the user open the document he/she can see only the data that its relevant to this username. More info here and here
For example:
user1 -> can see only UK data
user2 -> can see UK and USA data
user3 -> can see all the data
... etc
The web app and the desktop app are the same. The web client provide same level of interaction as the desktop so you can slice and dice your data as you want
4.1 QV desktop (personal edition) is free but you can open up to 5 qvw files which are not "yours" (not created with the current instance of the personal edition) and the clients need to install it locally on their computers
4.2 QV server is not free. With QV server all the clients are accessing the QV apps via the browser. You (as administrator) are buying the licenses from Qlik Partner and it's up to you if you want to charge your customers or not (and how much)
I am working on a project which is migrating some legacy SQL Server 2000 instances to SQL Server 2012. As you read word legacy, these databases are used by some VB based desktop applications. It has around 4000+ users and application is rated GOLD (means it has to be up 24x7)
Summary again
Desktop exe Installed VB applications -> SQL Server 2000
Target State
Desktop exe Installed VB applications -> SQL Server 2012
Application uses a config file that contains SQL Server details that it connects to. So once data move to new SQL Server, this config file needs to be changed with new server details.
I have been told that SQL Server 2000 can't migrate directly. It should first go to SQL Server 2008 and then SQL Server 2012. Please correct if this is not right understanding?
My problem is around Implementation Plan for this task in production. I can't move all users in one go means I would be migrating 100 users first and then few other hundreds and finally all left. Which means some users might start using SQL Server 2012 while other still working with SQL Server 2000. The reason I don't want everything in one go because it's too risky in case of any glitch and because application has to be up 24x7 it's not possible to bring down the applications and update config files on each user's desktop.
But if I allow 2000 and 2012 running together (say 1 week until all users move), it will make these databases out of sync and I don't think they can be merged later because both databases may be having same primary keys assigned to different data.
I can't bring the application down and take 4 hours outage to allow all users move to new databases in one shot because application has to be up 24x7.
Can any one recommend any approach that generally companies take to migrate SQL Server without outage like I stated above with keeping data consistency?
The easiest way to handle this is to create a new 2012 instance and create a database from a restore of the 2000 database. Then have replication between the 2 databases so that changes in either database will be published to the other that way your primary keys stay in sync. You will have to be down for a short period where you do the backup and restore to move all the data but assuming the 2 servers are co-located then it should only be a matter of minutes. Then once all your users have been migrated just turn off the 2000 server.
Post Upgrade, Client tools (Deski & Webi) are using US date format (MM/DD/YYYY). This is causing issues as users are earlier used to enter/view dates in UK date format (DD/MM/YYYY). We have updated regional settings on users machine to make sure it is UK format. Still in client tools it is not reflecting. How to resolve this?
I have an web app with some static reports that is running with SQL Server 2012 Web Edition and I dont want the impact of a report process on usage of the app.
So, I decide to split the database:
Database Master - With all data. Used for all web app precess, except the reports
Database X - With all data from the client X. Used only for report and updated every day.
Database Z - With all data from the client Z. Used only for report and updated every day.
Database Y - With all data from the client Y. Used only for report and updated every day.
There is no limitation number of database that could have.
What would be the best way?
-Cubes with Analises Services? I think I cant use this solution with Web Edition.
-Snapshot databases? Maybe in another server?
-Another solution?
Tks.
I could solve my problem using the SSIS (Integration Services) with Visual Studio
I create the Azure SQL databases with table that I want to public to my client
In SSIS I created packages for each client with their connection to Azure database. Also created a variable with the client ID that will be used by the filters.
Published the project in Integration Services Catalog and add JOBs to execute the packages every midnight.
For my clients I give the Azure credential (read-only) that will be used in Excel PowerPivot
Here is a link to a good SSIS tutorial. It worth for who has similar problem or need to migrate/extract/transform data. You can also generate Excel sheets.
SSIS tutorial with SQL Azure
We have a website we would like to transfer to our Server 2008, IIS7 site which uses NOPCommerce. We imported the database, set up the web.config and the database connects. The issue, it seems, is that it's not pulling the data.
For example: The registration page should be like:
First Name
Last Name
Gender
Birth Date
Instead its like
account.firstname
account.lastname
account.gender
account.dob
We ensured the site has proper access to the DB and it does connect(it yields an error page if it doesn't)
Anyone have any ideas?
Seems the issue was related to mounting the database. It seems the primary keys were set to the lowest available value instead of the proper one,