This post explains you very basic error that you get rarely and solution to that error,
Error: “Windows could not start the SQL Server on Local Computer. For more information, review the System Event log”.
The below error message will appear when your SQL Server evaluation period is expired.
Check the information in Event Viewer.
Buy the server and use the product key.
You can visit Maintenance in SQL Server installation and can upgrade.
This blog post explains the issue that we usually face while dropping the users from the database and how can we resolve the issue.
We can create a user for database easily by any of the following user types,
If we want to drop the user then we can write drop statement but it will throw a below error in case the user owned any of the schemas.
Msg 15138, Level 16, State 1, Line 20
The database principal owns a schema in the database, and cannot be dropped.
To resolve the issue, Follow the below steps.
Step 1: Check the schema that owned by the user.
FROM sys.schemas s
WHERE s.principal_id = USER_ID(‘Username’)
Step 2: Change the schema back to dbo.
ALTER AUTHORIZATION ON SCHEMA::<schemaname> TO dbo;
Step 3: Drop the user
DROP USER <username>
This post explains that what are the basic errors that you could encounter during the configuration of stretch database in SQL Server 2016 and how can you overcome those errors.
Check the below error,
Check my article on Technet wiki for a solution for the above issue.
This post explains a very simple error message that we may face if any issue with a shared dataset.
For example, take a below scenario
You have a shared dataset deployed to the report manager portal. The name of the dataset is Sales and you need to build a mobile report using Sales shared dataset.
When you use the Sales Shared Dataset from mobile report publisher, you may get an error message if any issue with the query used in Shared dataset or data source issue. The error message usually will say DataSet1 even though we used the proper name for the shared dataset.
It is because the shared dataset by default considering the name ‘DataSet1’ when you create a dataset. It can be identified and modified if you open the dataset file in notepad.
Have you seen this scenario? Share your comments below.
I got a below error message when I execute the report. The error message is very straight forward and it highlights the exact issue.
Basically, this error occurred due to different data types. There are many situations where we get this error so I thought to document this scenario.
An error occurred during local report processing.
An error has occurred during report processing.
The processing of FilterExpression for the dataset ‘Dataset1’ cannot be performed. Cannot compare data of types System.Decimal and System.Double. Please check the data type returned by the FilterExpression.
In Dataset1, I used a filter property and filtered “Unit Price” greater than 12. When I choose Unit Price column, it automatically picked the data type as float as it has values like xxx.xx in table.
The Original data type of the Unit Price column in the database is different, it is money data type. There is a mismatch of the data type.
There are two ways to handle this issue.
1. We can filter the value (Unit Price > 12) in script level and directly pass the script in dataset Instead of using dataset filter properties. We also will get good performance. Check my post on …..
2. If we want to use the dataset filter then we need to convert the unit price column into SSRS supported data types, in this case, float.
convert(float,[UnitPrice]) as UnitPrice
Available data types in dataset filter.