Here are a few simple steps of how you can load data from a .blg file into a SQL server DB Create empty DB; the first load will create all required tables Create ODBC DSN for this DB Load .blg file like this: relog “C:\PerfLogs\<fileName>.blg” -f SQL -o SQL:<DSN>!<SomeDescription> Advertisements
Archives for August, 2011
After implementing Database Mail correctly (send test e-mail). You might think you’re done after adding an operator to send emails if a job fail. Wrong You also need to enable your mail profile. Right click SQL Server Agent; Chose properties; click Alert System — Check Enable Mail Profile
Imagine, you lose the disk where your master DB is located on. It can happen to the best of us. Today it happened to me. Luckily, we had a copy of all DB files. Don’t ask why. This is what needs to be done: Stop panicking; SQL Server is not sensitive to emotions Copy all […]
Today I needed to perform following command prior to deleting a file of TEMPDB: DBCC SHRINKFILE (N’tempdev02′ , EMPTYFILE) But received following error: DBCC SHRINKFILE: Page could not be moved because it is a work table page. Apparantly, in most cases work tables are related to Query Plans. So running following DBCC solved my problem: […]
After migration from SQL2005 to SQL2008R2 none of our SQL jobs ran successfully using the default SQL Server Agent Service account (Run as defined in the jobstep). However using a proxy account, linked to a credential that impersonates the same SQL Server Agent service account, everything runs fine. We solved this issue by explicitly grant […]
After setting up a linked server to oracle, the connection was tested successfully. But when using the linked server in an openquery, following error message was generated: “Cannot get the column information from OLE DB provider “OraOLEDB.Oracle” for linked server.” Solution was to check the “Allow inprocess” option in the Oracle provider properties.
We recently did some tests with SSD because write response time of TEMPDB was below expectations. Our first test was very promising. Our 224 GB SSD disk was used to store 12 x 1GB TEMPDB files on. Read as well as write response times were well below 5ms/transfer. In our enthusiasm we also added our […]