I got this message from the 2012 version of the console after installing the Power Tools found here:
http://visualstudiogallery.msdn.microsoft.com/b1ef7eb2-e084-4cb8-9bc7-06c3bad9148f
The problem was that I was not a sysadmin in the SQL instance, once I fixed that the error went away.
Ever wonder why when you click on the green line in SSIS the Data Flow Path Editor doesn't actually let you edit anything? I did. Then I realized I needed to make the changes I wanted in the source task by right-clicking it and selecting Show Advanced Editor.
Today I got an exception in a report using SQL Server Reporting Services 2008 R2, but only when attempting to go to the last page of a large report: The report execution sgjahs45wg5vkmi05lq4zaee has expired or cannot be found.;Digging into the logs I found this:library!ReportServer_0... e ERROR: Throwing Microsoft.ReportingServices... , An error occurred within the report server database. This may be due to a connection failure, ......
For anybody getting an arithmetic overflow error in Microsoft.Data.Schema.TSqlTasks.targets in Visual Studio 2010, what resolved the problem for me was deleting the schema comparison file in my database project and then getting it from TFS again. I guess it must have been corrupted somehow.
UPDATE: That only worked temporarily, the error came back when getting latest from TFS and alternatively when opening a schema comparison in a different database project. Ugh.
In case anyone is storing their files as blobs in SQL Server and is interested in the best way to export them, check this out:
I have two Great Plains databases, let's call them DB1A and DB1B, that are schematically identical and the data is 99% identical but DB1B has a tiny bit more data. I'm trying to optimize a very complex query that uses views nested in views and is way too long to post all of here. The query was averaging 1 min 43 sec before I started. I noticed that all of the tables involved were heaps (Microsoft's fault, not mine) so I started converting them to clustered one by one, checking the plans and parallelism ......
I recently discovered that creating indexes in one of my production databases was causing deadlocks. My problem was that I wasn't using ONLINE=ON when I was creating the index. Check out the BOL for more information.
If you're like me you had at one time connected one of your Reporting Services instances to a report server database that was already in use by another instance. This allows the instance to show up in the Scale-out Deployment section of the Reporting Services Configuration Manager. My problem was that the server that got joined to the original server was no longer available as it had been repurposed, and when I clicked Remove Server to remove it from my scale-out it would fail because it couldn't ......
If you're wondering how to migrate your SharePoint databases to a new server, this Microsoft article is actually pretty useful, though still overly complex like most of their other articles. http://technet.microsoft.co... The one thing I would change is that they seem to recommend installing SQL Server Configuration Manager on web servers, when all that was needed in my case was to add an entry to the hosts file on the SharePoint web server that used the IP address of the ......
I have a real-time reporting server with a database which is basically a copy of my production database, but it's populated using transactional replication and replication only copies the primary keys over, i.e. none of the secondary indexes are included. So what I do is every time I need to recreate replication--which is every deployment with schema changes--I script out DROPs and CREATEs for all the reporting indexes I've created and then run the script after replication has been recreated. The ......