Microsoft SQL Server
If there is no much useful information in v$session_longops and space for the segment is already allocated how to get the same “rows completed” value of worker status as in intercative mode but using sql script? With small modification of example from the documentation I came with the PL/SQL block to get value of one Data Pump Import worker status attributes…
I just recently faced an issue on how to automate the Workflow Mailer override address for development and testing environments during the EBS cloning process. The problem is that the only official way to set the override address in the latest ATG releases is to go through the OAM portal and change the override email via the GUI interface. I came to this solution.
I’m here at the PASS Community Summit 2010 in Seattle, WA. This happens to be the largest SQL Server conference in the world with regards to content, attendees and Microsoft participation. There have been several announcements made in today’s keynote, few of which were just waiting to be blogged about from the insiders since earlier this year. First of which is the release of SQL Server 2008 R2 Parallel Data Warehouse.
As I’ve already gone thru building a Windows Server 2008 cluster in this blog post, let’s have a look at installing SQL Server 2008. Whether you’re looking at R2 or non-R2 versions of both Windows Server 2008 and SQL Server 2008, the steps are almost the same except for some PowerShell support for Windows Server 2008 on the Clustering side and whether or not you’re dealing with Hyper-V LiveMigration as part of your cluster (this, however is beyond the scope of this blog post).
I’ve recently learned that Chris Date is giving a three days seminar. It must be one of the unique opportunities to learn from the world renown expert in relational database theory. The seminar title is “How to Write Correct SQL and Know It: A Relational Approach to SQL”. It’s focused on writing reliable SQL. While SQL has been designed as a simple access interface to relational data, it turned out to be quite complex and requires your to follow a certain disciplines to produce truly reliable SQL code — relational discipline.
OpenSQLCamp was a huge success! I took videos of most of the sessions. The links to the videos are in this post. Enjoy!
One of our clients has a public web page and they needed to ensure that it is always up and accessible. Pythian already has a monitoring stack that includes website and pages monitoring. I wondered if this could be done from SQL Server using built-in Windows modules to access external web resources. There are various the methods we can use.
I had an opportunity over the past few days to attempt to use Microsoft’s Server Management Objects (SMO) with Perl to manage a SQL Server 2005 DB. To make a long story into a short post, I blundered into the Win32::CLR module on CPAN, a little gem from Toshiyuki Yamato. Here is all you need to get started.
Here is a must-read whitepaper describing SQL Server Scheduling and how to interpret and diagnose Errors 17883, 17884, 17887, and 17888; please look here How To Diagnose and Correct Errors 17883, 17884, 17887, and 17888. We had a client having same issue. The client runs a busy online business with thousands of connected users; databases sometimes include more than half a million tables. We had a healthy counters and server didn’t seem to suffer from memory or I/O bottlenecks. We did suspect, that it is something to do with SQL Server internals, as we also received fatal exceptions pertaining to SPIDs <50 (system processes). If you face similar issues, you should install the latest service pack and cumulative update, and check if you have any resource bottlenecks. You can try trace T2330 as well, and if you still get errors or dumps, then you had better open a case with Microsoft Support to analyze the dumps and provide a resolution.
This is a little tip for those who develop or debug SSIS packages. In SQL Server Integration services, User namespace variables are assigned values that are used across the package. When developing, testing or debugging packages, we assign multiple values to those variables to test different scenarios. This is done using the variables window. However, SSIS Script tasks can allow us to key in values for selected variables in run time. This looks more fun and keeps us from taking chances when we forget assigning variables’ values.