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.
Sometimes you have very important tables that you need to be alerted if there are any changes made to the data. You can setup a trigger that sends you an email whenever an insert/delete/update is done to any of the data.
Yesterday was the Cleveland edition of SQL Saturday. If you do not know what SQL Saturday is, you really need to follow this link: https://sqlsaturday.com/default.aspx
From their site: “Free, high quality, 1-day, SQL Server Training events. You’ll find it’s a great way to spend a Saturday.” If you go to their site, you can also download slides, pdf’s and scripts from previous sessions from all of the other cities. I also recommend you sign up approx 3 months before the day of the class so you do not get shut out. Today I am going to give you a rundown on the sessions I attended.
If you need to find out who is currently connected to your databases or how many users are currently connected, the two scripts below are life savers.
If you try and create an Integration Services Catalog and you receive the error SSISDBBackup.bak could not be accessed, it could be because you do not have Integration Services installed on your SQL Server instance.