MSBI Tutor

Our industry-leading conference is coming to Bengaluru. Don’t miss the very latest in cloud technologies and developer tools with guest speakers, industry experts, and more. Microsoft Ignite The Tour brings the very best of Microsoft Ignite to a city near you. The tour provides technical training led by Microsoft experts and your community. You’ll learn new ways to build solutions, migrate and manage infrastructure, and connect with local industry leaders and peers. Register now Agenda Wednesday, April 8, 2020 9:00 AM–10:45 AM Registration, networking breakfast Check in, enjoy breakfast, and join us to kick off your learning in a casual atmosphere with your peers. Get a preview of what’s to come during the day and check out real-world transformation stories from various industries. 9:00 AM–6:45 PM The Hub: theater sessions, expert connections, expo, and more Take advantage of this central gathering place where you can liste...

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 अपराह्न ...

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

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

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.

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...

1. Open your SSIS project. 2. Right click on project and select project properties. 3. Go to general tab and select target SQL server version, Click on OK 4. Again right click and project and select build Build was success 6. Right click on project and deploy Deployment wizard will open as shown in bellow 7. Select deployment mode as shown in bellow.  Click on next 8. Provide server and select SSISDB catalog path Click on next 9. Before deployment please check SSISDB catalog in SSMS. No project are available in SSISDB catalog as shown above. 10. Now click on deploy 11. Now deployment project appaired in SSISDB catalog