Featured Article(s)
Programmatically creating/updating list items on remote SharePoint server
Here is the scenario: You have a client application or Office application add-in that needs to write data to the SharePoint server. Obviously your server is hosted somewhere else but on your client machine; but you have all of the required login credentials to perform write on the sub-site of your interest. How do you go about creating/updating items on your SharePoint server from this client application?
SSWUG.ORG SelectViews SQL Server Show
The show today features RAID and Defrag tips, backup optimization with filegroups, baseline stats and industry news. Also, find out about virtual learning opportunities, the SQL tip, the developer/AJAX thoughts and much more.
[Watch the Show Here]
Stopping to Take Stock
Interestingly, we’ve been playing with different tools that aim to accomplish the same things. From performance reporting to best practices to management of different aspects of SQL Server… "interestingly" because they’re actually showing different results in some cases. With some of the feedback elements, the results are actually suggestive of a hardware failure, others all things are OK, still others indicate that simple maintenance is needed to optimize the system.
This has me worried, frankly. It seems to me, especially in cases where the suggestion is that an impending serious failure is on the horizon, that the results of packages should be largely similar. Not so, apparently. We’ve had two packages now suggest these types of major issues in different areas and suggest recovery techniques. When we drop back to SQL Server native testing and validation routines to prove out the issues that were approaching, suddenly the issues are there.
What??! Yes, I get it – there could be transient issues. But really, not like this and not multiple times in different areas with different tools reporting different results. Just doesn’t make sense to me.
I tell you all this to say two things:
First, before you take drastic recovery steps in response to a tool’s findings – ANY tool, be it SQL Server native utilities, third party tools, anything – be sure to confirm your findings and test your approach before you take drastic action. Sort of like getting a second opinion.
Second, I’ll keep you posted if we can figure out why the difference in results. I don’t have definitive outcomes at this point, it’s still unfolding. I’ll keep you posted.
Do you see things like this? It’s a bit maddening.
Featured White Paper(s)
Migrating DTS Packages to Integration Services
SQL Server Integration Services (SSIS) brings a revolutionary concept of enterprise-class ETL to the masses. The engine is ro… (read more)