A community of more than 1,600,000 database professionals and growing
The Voice of the DBA
Lots of IT professionals I know have moved to laptops for their daily work. This allows them to keep their work handy, no matter where they are. If they need to work from home, or on a trip, they have their tools with them. It's a good move for many people, but I wonder if it's what the majority of professionals want. As a side note, if you have a work laptop, with work data, you ought to be using whole disk encryption.
When I worked as a production DBA, it was handy to have a laptop to connect to work from home and check on things. However I felt this was a double edged sword, with the responsibility of carrying the laptop with me, and the expectations of management that I would be "more available" than if I didn't have a portable work machine.
Recently I thought about this when I saw a release for a new desktop PC that is "no wider than a golf ball", the new ThinkCentre M93 from Lenovo. It's small, and powerful, with enough power for many developers and administrators that might work in the technology area. It's also one of those machines that I might consider portable.
To me this might be the best of both worlds. Something that's a desktop, removing me from the responsibility and obligation to take it home with me every night. However small enough that if I did need to work at home, to monitor a process, or get something done away from the office, I could pack it up and use it at home.
I wonder how many of you have laptops from work, or desktops, and if you prefer one or the other. I used to appreciate an employer picking up the expense of a laptop, but these days I'd prefer to buy my own and let the employer keep their equipment in the office, and out of the rest of my life.
Data Analysis Expressions (DAX), originally the formula language for PowerPivot workbooks, can also be used within the MDX query window of SSMS to directly access data from a tabular SSAS database, an in-memory database that uses the xVelocity analytics engine and compression. Robert Sheldon shows how easy it is to retrieve data from a tabular database. More »
SQL Server Execution Plans shows you what's going on behind the scenes in SQL Server. They can provide you with a wealth of information on how your queries are being executed by SQL Server, including: Which indexes are being used, and where no indexes are being used at all. How the data is being retrieved, and joined, from the tables defined in your query. How aggregations in GROUP BY queries are put together. Grab your copy today from Amazon!
Yesterday's Question of the Day
(by Steve Jones):
You have enabled TDE on an important database in your organization. While preparing your DR plan, you realize that you need to make backups of certain objects in order to be able to restore your TDE database on a new instance at your remote location. Which objects do you need to back up?
Answer: the certificate that protects the DEK
Explanation: The only object you need is the certificate protecting the TDE Database Encryption Key (DEK). The DEK is inside the backup, and the master key in the master database is not required.
SQL Server 2012 Data Integration Recipes provides focused and practical solutions to real world problems of data integration. Need to import data into SQL Server from an outside source? Need to export data and send it to another system? SQL Server 2012 Data Integration Recipes has your back. You'll find solutions for importing from Microsoft Office data stores such as Excel and Access, from text files such as CSV files, from XML, from other database brands such as Oracle and MySQL, and even from other SQL Server databases. You'll learn techniques for managing metadata, transforming data to meet the needs of the target system, handling exceptions and errors, and much more.
The following script will interrogate the orphaned users in each database on a particular server. All records from sysusers where the record contains a SID are selected, before using suser_sname(SID), which returns the login name associated with a security identification number (SID). If the returned value is null, the database user is not attached to a valid login.
Various filters are subsequently applied to exclude rows not required eg database and application roles.
A temporary table is then populated with data from each database using the sp_MSforeachdb procedure.
- We are running SQL2008R2 64 bit standard version.
One of the application encountered (via Tomcat service) error " database.pool.ConnectionPool Exception: com.microsoft.sqlserver.jdbc.SQLServerException: The...
This newsletter was sent to you because you signed up at SQLServerCentral.com.
Feel free to forward this to any colleagues that you think might be interested.
If you have received this email from a colleague, you can register to receive it here.