We have sort of integrated another SQL database with the NAV database.
When certain fields on the customer card are changed the customer record gets copied to a new table. A SQL script runs every 60 seconds to find these records and imports them into the other SQL database.
I would like this to happen much faster than 60 seconds. We can't make the increments and shorter than that. I was told we can't call the SQL script from NAV so what other ways can we reduce that time?
0
Comments
- you copy changed customers to kind of a queue table
- then every 60 seconds a SQL script runs and copies them to another database, and there 60 seconds is the limit?
if so, to decrease this limit, you could use NAS with a timer to check the queue table, and if NAS finds records, it starts processing them (maybe by calling a stored procedure on the other database, but you will need something to connect to it, ADO could help you with this)
Can NAS call stored procedures?
I described it here (and on my blog).
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
Bill
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!