I tried creating a webservice task within SSIS, and I kept getting errors. The provider said all of my connections were setup correctly, so they did not know what was wrong. The problem turned out to be something very simple.
You may have a big file or a large database table that you want to split up into different csv files. Instead of writing multiple queries for the different cases, you can use Conditional Split within SSIS to accomplish this task. There are also a multitude of other scenarios you can use it for.
The deadline has passed for SQL Server 2008 and prior to be supported so now you have to migrate the databases to newer versions, but you cannot connect because the person who knows the SA password has left or it has been forgotten. Using PSEXEC you can recover access and login!
I recently had a SQL Agent job fail, but it did not email me. Looking at the job history, it says:
The job failed. The Job was invoked by Schedule 10 (xxxx DB backup.Full Backup). The last step to run was step 1 (Full Backup). NOTE: Failed to notify 'Jim' via email.
Have you ever created a query, exported the results and then closed the query tab, not saving because it was just a one time query? Then 5 minutes later you get a call saying, “oh, can you run it again with these values?”. Now you have to wrack your brain and figure out what you previously created.
Often when you are working in SQL Server Management Studio (SSMS), tables, views, and other objects will get highlighted with a red squiggly line like SSMS does not know if the object exists or not in the database.
One day I was trying to query Oracle data through a SQL Server Linked Server and received the following error:
Msg 7354, Level 16, State 1, Line 1 The OLE DB provider "OraOLEDB.Oracle" for linked server "CEGIS" supplied invalid metadata for column "SHAPE". The data type is not supported.