No bootable medium found!” error in Virtual Box

I was using Ubuntu on Virtual Box, I was constantly getting errors
"Fatal: No bootable medium found! System halted."

I used VM to install and test new software programs before I put those in my daily work horse. Long story short.

Change the Setting to below it should work

User ‘public’ does not have permission to run DBCC showfilestats for database ‘ testing’

User ‘public’ does not have permission to run DBCC showfilestats for database ‘ testing’

This error message is raised when your user account does not have the db_owner role of a database meaning you are not the owner of the database; and you try to open the properties dialog box of a database in SSMS 2008.

User ‘<User>’ does not have permission to run DBCC showfilestats for database ‘<Database Name> ‘.

Cause:

This happens when you right click on a database in SSMS and click properties of the database; In response SQL Server 2008 runs the DBCC SHOWFILESTATS command to fetch the UsedSpace property and the AvailableSpace property. Because the user is not the db_owner, the user does not have permission to run the DBCC SHOWFILESTATS command. Therefore, the user cannot open the Properties dialog box in SSMS 2008.

Resolution:

Processing Cube Dimension Incrementally

I didn't find much about how to process dimensions incrementally in a cube. To be clear, I am focusing on processing cube dimensions not dimension table. I have seen and work with different setting of the cube and work with "Process Update".

This process the data incrementally in the Cube dimensions.

If you using SSIS drag and drop analysis service item and set the setting as "Process Update".

sqlmanagment studio: cannot find one or more components. Please reinstall the application

 

This can 

(after installing vs2013)

SSMS Depends on Visual Studio 2010 IDE, which if not installed the SQL Server Setup will do, but if any version is present, the setup will ignore it, even at repair

Re Install, I figured that the SSMS needs Visual Studio 10 IDE to run, which I've removed by mistake after uninstalling VS 2010.

So, I Opened the Setup Media and searched for Visual Studio Setup. The .msi file run quitly and Filled the missing parts, and the Management Studio Run OK.

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/3dd6f643-720f-4878-9594-894da73efd46/sqlmanagment-studio-cannot-find-one-or-more-components-please-reinstall-the-application-after?referrer=http://social.msdn.microsoft.com/Forums/sqlserver/en-US/3dd6f643-720f-4878-9594-894da73efd46/sqlmanagment-studio-cannot-find-one-or-more-components-please-reinstall-the-application-after?forum=sqlexpress 

I found that if you do not have the CD you can get the VS 2010 IDE component that SSMS 2012 relies on here:

http://www.microsoft.com/en-us/download/confirmation.aspx?id=1366

It's called Microsoft Visual Studio 2010 Shell (Isolated)

After installing that, SSMS runs for me again, Microsoft needs to add this install into their repair logic!

Remove duplicates from SQL Table

Alot of time duplicates needed to be deleted. 

Case scenario,  When one reocrd is touched it can have same data with only different dates and may end up with duplicates when joining with Id

I normally use the below script to clean it off.

with cte as (
 select
Id ,row_number()over(partition by Id order by Id ) rn
from dbo.Table
)

DELETE from cte where rn>1

The Size Specified for a Binding too Small (SSAS Cube)

Getting an error when processing the Cube (SSAS) "Errors in the back-end database access module. The size specified for a binding was too small, resulting in one or more column values being truncated. Errors in the OLAP storage engine.”  This error is due to the size of the Attribute exceeds the Data Size defined in the attribute.

I have seen this error comes at two places that is 
1) when data size in physical fact table is changed.
2) when data size in physical dimension table is changed.

Resolution for

1) If dimensions are processing successfully only seeing the error when Cube itself is processed. Open the data source view right click and refresh. This will fix the cube. Now deploy the Cube and re-process.

2) If error comes when processing dimensions. This can be solved easily by two ways.
    
    A) If it is simple Dimension, delete and create new dimension link the keys with Fact.
    B) If the above is not an option then check data type of each attribute of the dimension, match this with physical dimension table. and update the data type in the dimension attribute. 

After updating Data types re-process the dimensions. 
Have a happy day.