Wednesday, January 25, 2012
Great tips for optimizing SSIS source queries.
Luckily, T-SQL gives us a brilliant query hint to help avoid this.
OPTION (FAST 10000)
This hint means that it will choose a query which will optimise for the first 10,000 rows – the default SSIS buffer size. And the effect can be quite significant.
Monday, January 23, 2012
If you’re having issues with SSIS 2008 R2 logging in script tasks, it’s most likely because syntax has changed.
See this link on how to use ComponentMetadata.FireProgress instead of Dts.FireProgress.
Friday, January 20, 2012
sync SSRS report between two report servers
Sync reports between two SSRS servers.
Download rdls from SSRS to local PC.
Upload files to a SSRS server
Attach datasources automatically on upload(Data source name given in the report must exist on server)"
Thursday, January 19, 2012
Microsoft Visual Studio
The report definition failed to load: There is an error in XML document (5, 2).. Verify the report definition conforms to the correct schema.
If you get this, and are using Subversion for your Reporting Services development, you may have a corrupt data source file. The xml involved has nothing to do with rptproj, it is actually an item within, in this case the data source.
XML and Visual Studio are my two least favourite things when dealing with bugs.
Wednesday, January 18, 2012
Teo outlines some of the pros and cons of the new BI edition of SQL 2012.
About $10k per server vs. over $50k for Enterprise Edition is the biggest plus. It will provide all the features for Analysis Services previously found only in Enterprise, and gives a fully functional PowerPivot, Analysis Services & Reporting Services server to the SME’s.
From what I understand, the key driver for Microsoft making this change would have been the requirement of installing 2 separate instances of SQL for using both PowerPivot and Analysis Services (multidimensional or tabular) data stores. For those clients wishing to install 2 separate environments for those, the cost will end up being about $20k anyway, not including Sharepoint and DW SQL instances.
One limitation is the 2-socket configuration limit. Another is the per-user licensing scheme, which could leave companies with 50-200 users in a grey zone. Enterprise or BI?
The licensing model for private clouds seems a bit more appealing from an ROI perspective. Invest in SQL Enterprise and deploy an unlimited # of VMs. The disadvantage is the need to license the entire server farm for SQL Enterprise + Software Assurance.
Microsoft also seems to be shutting out AMD with the new licensing scheme, and targeting Intel’s Q2 release of their new 2-socket chipset.
Now that MS has moved to a core licensing model + user vs CPU socket, will this change the R&D direction of CPU manufacturers? Will they now focus their efforts more on GPU processing? What if a PC only had 1 core & 1 socket, but multiple GPUs and something else besides a CPU to handle the more precise calculations?
Thursday, January 12, 2012
Actually, it should be any O/S, if VMs are available… an interesting twist on cannibalizing their existing Windows Azure platform.
To date, Microsoft has been balking at customer requests to add persistent VMs to Azure, hoping to get customers to develop Azure apps from scratch instead. But the lack of the ability to host apps like SharePoint and other third-party business applications with persistence was a deal breaker for a number of business users who were unwilling to consider Azure until Microsoft added this support, one of my contacts said.
Tuesday, January 10, 2012