View Complete Post
I am converting reports developed in SSRS 2005 into SSRS 2008. In the report design interface I have several rows and columans of data that calculate count or rate. In addition to rows and columns, I have around ten hidden tablixes in which report expression
calls hidden codes inside tablix to perform calculation with main report. My problem is when I set hidden tablix propert into hide, I am not getting correct calculation in my report. when I change tablix property from hidden to show I will get correct
calculation but I do not want to see those hidden tablixes in my report page. Is there any way you can still call expressions inside hidden tablixes without turning on tablix property show in SSRS 2008? Is it a bug in SSRS 2008 reporting system?
Please help me out!!
My operating system is windows vista.
We're moving a SQL 2005/Windows 2003 process to SQL 2008 R2/Windows 2008 and are having a devil of a time making it work. It runs in 2005 just dandy. SQL Server 2008 R2 (64-bit) is running on a virtual machine, everything is new.
Standard SQL server install. No service packs.
I'm running several stored procedures from one script from SSMS. The script pretty much bombs after the same Stored Proc everytime, although not always. The sql error message is as follows:
Why would it disconnect and reconnect in the middle of the script?
Perhaps a red herring but the one of the steps before the error happens is a clr stored proc job surrounded by SQL code that turns Trustworthy On/Changes Owner to 'sa' and back (Owner to NT Authority\System / Trustworthy
A real head scratcher.
Error in Windows Application Log
Faulting application name: sqlservr.exe, version: 2009.100.1600.1, time stamp: 0x4bb6b40b<
Let's start a very intresting thread here:
As you all know moving the database from one server(2000, 2005, 2008) to (2000, 20005, 20008) is not a big deal and can be done in many ways like backup-restore, attcah-detach, and most easy (some time very complex:-)).
Here i wanna discuss an issue which i have faced.
I have two instances of SQL server 2008, i have created a new database Test in one instance, created few logins and mapped to Test database with some permissions for this Test database.
Now i used copy database wizard to copy this test database to other instance, i sucessfully went through the wizard and selected SQL server object method to copy the Test database in other instance then i followed the remaing wizard, i selected the logins which i have created for the Test database and finnaly i reached the finish button i clicked finished and the copy of database completed sucessfully. I verified that Test dabase was there in other instance with the logins which i have created. So easy i was happy:-)
Problem: Some other day i wanted to copy AdventureWork database to the other instance of SQl server i was happy that its a very easy task i followed the same steps above(to copy the Test database ) and every thing went in the same way and i clicked finish to complete the wizard it took some time
I have a series of Crystal Reports that I can view/edit using Visual Studio 2005 with no issues. The method I'm using is to simply click on the *.rpt file and it opens in the VS crystal editor with no issues. The problem I'm having is that we are upgrading to Visual Studio 2008, and when I open the *.rpt file in 2008 it opens as a binary file. I guess I'm used to everything else in Visual Studio prompting me to convert the older version to the newer version, so I'm not sure what to do in this case.
Is this normal? Is there an easy conversion method that I'm simply overlooking? Am I screwed? Who invented liquid soap, and why?
Answers to any of these questions would be greatly appreciated...
Hi and thanks.
I'm getting an error on serveral reports that I built in VWD2005 (express) using the reportviewer control. Trying to edit the rdlc file in VS2010, VS2010 asks if i want to convert the file to RDLC 2008 format and I click ok. When I build the site, I get this error (and of course also when the report is ran):
Error 1 The report definition is not valid. Details: The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition' which cannot be upgraded. C:\inetpub\wwwroot\mastercardlcm\Reports\WorkLists\OpenSRStatus.rdlc 1
Here is my web.config concerning the RDLC assemblies, etc.
<add path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=220.127.116.11, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>
<add assembly="Microsoft.ReportViewer.WebForms, Version=18.104.22.168, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
Am in the process learning C#, My instructor uses Visual C# 2005 Express and on my side I have Visual Studio 2008 Pro.
Do you think it will affect me in my Coding practice due to the different IDE Versions? Wha do I have to heed when coding?
i cant install sql server 2005 nor 2008 on my windows 7 os
i read about somthing like adding new account when installing sql 2008 to provision the server or so, but didnt know how,,,
can you plz help me??
import/export wizard in 2000 had lots of options.
I could copy databases without a care in the world. Including constraints, stored proc., AND the data, etc.
Now, with v2008, the wizard is dumbed down too much. It's a "stupid" copy function that fails on the first constraint it meets.
"Copy database.." is not an option here: it needs sysadmin on both source and destination server.
Re-adding the constraints manually is not an option either: the database is WAY too large.
I'm actually hoping there is a temporary bug in the import/export wizard. Each option (and you have THREE...) returns with a new error.
Googling, I found I am not alone:
This post is exactly my situation. Here's what his post says: (bolded key parts)
"Hi I'm trying to get used to sql server 2008 having been
forced to upgrade by my isp. I need to back up my key db on a weekly
remote schedule, so have been trying to use ssms to export data from my
remote db to a local copy. Firstly I created a new empty db on
the local machine. Then I scripted the structure of the db on the
remote machine and ran the resulting query on the local machin