Posts

Showing posts from December, 2019

GETDATE() in local language

DECLARE @date DATETIME = GETDATE() SELECT  FORMAT( @date,'dddd, MMMM dd, yyyy hh:mm:ss tt','en-US')    AS 'US',  FORMAT( @date,'dddd, MMMM dd, yyyy hh:mm:ss tt','hi-IN')    AS 'Hindi',  FORMAT( @date,'dddd, MMMM dd, yyyy hh:mm:ss tt','kn-IN')   AS 'Kannada',   FORMAT( @date,'dddd, MMMM dd, yyyy hh:mm:ss tt','te-IN')   AS 'Telugu',     FORMAT( @date,'dddd, MMMM dd, yyyy hh:mm:ss tt','ta-IN')   AS 'Tamil',     FORMAT( @date,'dddd, MMMM dd, yyyy hh:mm:ss tt','or-IN')   AS 'Odia',     FORMAT( @date,'dddd, MMMM dd, yyyy hh:mm:ss tt','ml-IN')   AS 'Malayalam',     FORMAT( @date,'dddd, MMMM dd, yyyy hh:mm:ss tt','gu-IN')   AS 'Gujarati' Results: US Hindi Friday, December 13, 2019 06:06:46 PM शुक्रवार, दिसम्बर 13, 2019 06:06:46 अपराह्न

The transaction log for database 'MSBITutor' is full. To find out why space in the log cannot be reused

Msg 9002, Level 17, State 2, Line 4 The transaction log for database 'MSBITutor' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases Cause: Due to database log free space Solution: Have made database recovery mode as simple from full mode

The database file with name 'SSISDB' already exists in directory

TITLE: Microsoft SQL Server Management Studio ------------------------------ The database file with name 'SSISDB' already exists in directory 'C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\'. Make sure there is no existing database file with the name 'SSISDB' under this directory and try again. (Microsoft.SqlServer.Management.IntegrationServices) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProductVersion=14.0.3026.27+((SQLServer2017-CU7).180510-1901)&LinkId=20476 ------------------------------ BUTTONS: OK ------------------------------ Solution: 1. Go to C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\ 2. Delete data files related to SSISDB 3. Try to create SSISDB again in SSIS catalogs

An item with the same key has already been added in SSIS package

TITLE: Microsoft Visual Studio ------------------------------ Failure saving package. ------------------------------ DDITIONAL INFORMATION: An item with the same key has already been added. (Microsoft.SqlServer.ManagedDTS) ------------------------------ BUTTONS: OK ------------------------------ Cause: Have created a two SSIS packages. One package having package level connection managers and another package having  project level connection. Solution: Have a removed package level connection in 1st package and it's working fine.

Exception deserializing the package "The process cannot access the file because it is being used by another process."

TITLE: Microsoft Visual Studio ------------------------------ Failed to start project ------------------------------ ADDITIONAL INFORMATION: Exception deserializing the package "The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process.". (Microsoft.DataTransformationServices.VsIntegration) ------------------------------ The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process. (mscorlib) ------------------------------ BUTTONS: OK ------------------------------ While running SSIS package i got the error “The process cannot access the file ‘*.ispac’ because it is being used by another process”. I tried to close SSDT and run it again but, I still got the same error while compiling. Then, after searching over internet, I got