Refresh with F5 does not work, but with CTRL + F5 works;
Good Morning,
We perform the migration from SQL Azure database to SQL Server.
We completed the successful migration, with the correct data and users.
One problem I understood is that after migrating the F5 (command to update the database), no longer works.
Example: I as an administrator, signed up a new connection.
The support user updates the database with the F5 and not updated.
Now, if you press CTRL + F5, it updates.
host RDM: Windows 7 / Windows 8 / Windows 10
RDM version: 11.1.9.0 (Beta)
SQL Server host: windows server 2008 Data Center
What can it be?
Tks.
All Comments (1)
When you moved your database from local to Azure did you create a new datasource for each user or simply change the existing data source to reference Azure instead?
The reason I ask is that the data is cached using a version schema that is tied to the database. If you moved the db via export/import the version schema will be reset (internal to SQL Server) and will throw off the caching machanism. CTRL + F5 (refresh) clears the client cache and starts over.
You have two options: CTRL + F5 every client (once) or delete the data source and add a new one on every client.
This is an edge case scenario, we could have a move detection mechanism where the database notifies the client to do a full-refresh instead. (in other words force a CTRL+F5) even if the client only hit F5. Unfortunately we don't yet have this mechanism in place.
Both will work, CTRL + F5 is the simplest.
Best regards,
Stéfane Lavergne