NauticalGent
Ignore List Poster Boy
- Local time
- Today, 04:55
- Joined
- Apr 27, 2015
- Messages
- 6,750
Figured I would provide a followup for any future searches.
My Command (company) already had SharePoint 2007 available so I set about trying to educate myself on how the two work together.
As a side-note, SQL/Citrex were non-starters. Our IT process is too cumbersome and by the time it would have been available I would be long gone and no one would remember why we asked for it in the first place. Such is the life of a unit that turns over so frequently.
I wanted to go whole hog with the SP integration and publish my app on the web, but lucky for me, we did not have that package. I use the term lucky because that technology now has very short future.
Long story short, I moved all the pertinent tables to SP and converted the seldom updated tables, like Look-Ups, to local tables. It worked rather well for my detachment in Rota, Spain (same server) but the detachment in the Middle East were still experiencing serious lag.
I played around with server-side filtering and linking GUID/List Views but the resynch process could still take up to 4 minutes.
Almost by accident I came across an article that explained how the 2010 caching feature, when enabled, improves performance...and how right they were! Updates are almost instantaneous even from the Middle East.
Very pleasantly surprised. It isn't a perfect solution, I still have some issues with dropped connections. But because the data never really leaves the server, we haven't experienced any corruption in over a year (knock on wood!)
Anyway, hopefully MS wont continue down the road of SP extinction and this fix will be viable option for a some time.
My Command (company) already had SharePoint 2007 available so I set about trying to educate myself on how the two work together.
As a side-note, SQL/Citrex were non-starters. Our IT process is too cumbersome and by the time it would have been available I would be long gone and no one would remember why we asked for it in the first place. Such is the life of a unit that turns over so frequently.
I wanted to go whole hog with the SP integration and publish my app on the web, but lucky for me, we did not have that package. I use the term lucky because that technology now has very short future.
Long story short, I moved all the pertinent tables to SP and converted the seldom updated tables, like Look-Ups, to local tables. It worked rather well for my detachment in Rota, Spain (same server) but the detachment in the Middle East were still experiencing serious lag.
I played around with server-side filtering and linking GUID/List Views but the resynch process could still take up to 4 minutes.
Almost by accident I came across an article that explained how the 2010 caching feature, when enabled, improves performance...and how right they were! Updates are almost instantaneous even from the Middle East.
Very pleasantly surprised. It isn't a perfect solution, I still have some issues with dropped connections. But because the data never really leaves the server, we haven't experienced any corruption in over a year (knock on wood!)
Anyway, hopefully MS wont continue down the road of SP extinction and this fix will be viable option for a some time.
