Share
ReportIf I start check links tonight in a test company will it have any affect on our users working in our LIVE environment if it does not finish tonight?
*This post is locked for comments
You’re offline. This is a read only version of the page.
If I start check links tonight in a test company will it have any affect on our users working in our LIVE environment if it does not finish tonight?
*This post is locked for comments
When running a check links process, the first and most essential recommendation would be the "backup" for both Dynamics and Company database. Since, in several cases, Check links encountered deleting records "especially when third party products are included" as well as inserting new records.
In this essence, I would not recommend kill the check links process although it is mostly intended to run several procedures on the company database per module.
I still can't see any problem in running check links per series, or at least several inter related series in your case (such as POP, SOP, Financial and Inventory for instance). Otherwise, you need to create a separate test environment with a separate SQL Server instance which might be a bit hard but safer.
One more essential point that might be more important in your case than the check links itself, consider the Size of your database, since I don't believe it is healthy at all to have as much as 180 gb ! All related processes will be affected accordingly.
Hope this helps,
does the DYNAMICS tables (shared between LIVE co. and TEST co) get touched in anyway and could they be damaged while users are in LIVE while Check Links is running on the TEST environment?
The database is about 180 gig
Hello everyone. I'm Christy and I work with Larry. We appear to have an issue with our SY00500 table and need to rename it and run CheckLinks to restore the batch header connections. To do that, we have to run the entire thing at one time. Our database is very large and we are trying to get a plan for how to do this with the least amount of user interruption. Looking at it from that perspective, what would be your approach? Also, if we were to stop it, are there any shared tables in the DYNAMICS database that would be damaged for the whole system if we did?
Normally it is best not to stop check links but if it is a test database no real harm can be done. The next big holiday is Thanksgiving so that does not help. Perhaps you could stop it at noon on Friday to give it 68 to complete assuming they start work at 8am on Monday. Would that be enough time? Are you running check links on the server? You can always use Task Manager to kill the GP process on the computer that is running check links. That will stop it. You would want to make a fresh copy of the test database. How big is this database?
Nothing more valuable to add for Mr. Richard's comments, though, I would have a suggestion in here.
Although I haven't seen any check links that would take more than 12 hours (per series), a good plan would be to perform check links per series on a scheduled daily base. (Let's say, you start with the Financial Series for instance at day one) that will basically provide two advantages; first, one series will mostly get done with less than 12 hours which will guarantee no slow performance for live users, and secondly, an approximate assessment will be clear on how long further series might take.
One more point to add, check links can be run with users logged in, accordingly, you could still have users working on Live company. Needless to say, you should still consider the slow performance mentioned by Mr. Richard.
It took over 48 hrs last time. We had a couple of issues with our database and we also had replication running. That may have been the main reason. So the only thing that will happen is our users may experince it running slower even if it is being ran on a TEST server? It doesn't touch any LIVE databases? How would you stop Check links? I thought you where forbiden to do that.
If it takes 48+ hours to run check links, that is one heck of database. That will be up to you. If your users complain about slow response time then by all means stop check links. If not, just let it continue to run.
Let me be a little specific in my question. We do have a test company on the same server and same instance of our LIVE company. If we have everyone get out of our TEST company and LIVE company today at 5 p.m. and started Check links in our TEST company, and If it is still running come Monday morning when everyone is ready to work in our LIVE company, will we have to stop check links or could we let it run while users are working in LIVE?
If your production companies and your test companies exist on separate servers, the answer would be NO. However, if the are installed under the same instance of SQL or are even on the same server the answer would be YES. In this case, there will I/O associated with all the data crunching that is occurring. It may not matter if you databases are fairley small and the check links procedure will be over by morning. Have you ever run check links before to give you an idea of how long it takes?
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,269
Super User 2024 Season 2
#2
Martin Dráb
230,198
Most Valuable Professional
#3
nmaenpaa
101,156
All responses (
Answers (