Most of us don't deal with sensors in our jobs. Or do we? So many devices are in use these days, with a wide variety of inputs that many of us might not realize that applications might be capturing some of this data, which is more akin to sensor data than manually entered data. I would suspect that the meta data might vastly exceed the amount of data entered in text boxes in many of our databases in the future. It might be location, time, action, event, or some other data that we store, manage, and link to data that users choose to submit.
The Black Hat conference took place recently and one of the sessions talks about the proliferation of cheap sensors that could be used to potentially track individuals without their knowledge. That's an interesting use of hacking skills, cheap technology, visualizations, and of course, lots of data. While there are plenty of scary privacy implications here, especially for criminal activity, I could see other uses as well.
Imagine that you work in a retail environment? You might want to know how people move around your store, potentially in order to redesign your store. What about industrial centers? Additional data about parts flowing has resulted in more efficient workflow, but with even more sensors and data, you might find new ways to improve productivity. UPS and FedEx have used technology to vastly increase their efficiency; how many other companies could take advantage of sensor data and find new ways to run their businesses.
I expect to see more and more data being collected in all sorts of organizations (commercial, government, and others) as more sensors and other hardware become inexpensive. Just as the decline in the cost of computers has enabled almost every organization to take advantage of their capabilities, I expect the new types of sensor data will allow data professionals new opportunities. All the additional data gives us the chance to perform all types of analysis, data mining, and more. It's a good time to be working in the data field, with new opportunities appearing every day.
In this article we'll take a look at the following Tips and Tricks for SSRS: Display Total Number of Pages while Navigating, Display Everything in a Single Page, Display Report Parameter Selection, Display No Rows Error Message, Page Settings for Optimal Printing. More »
If the transaction log autogrows rapidly, it can suggest that log backups are not being carried out frequently enough, or another resource may be preventing the log from truncating. This metric measures the number of transaction log files that are greater than 10 GB. The associated alert is raised when the number of files exceeds a specified threshold. More »
Standard best practise is to have auto create and auto update statistics set for SQL Server databases. But there... More »
Question of the Day
Today's Question (by Dwain Camps):
What is the difference between the following 2 queries:
SELECT ROW_NUMBER() OVER (ORDER BY NEWID())
SELECT ROW_NUMBER() OVER (ORDER BY (SELECT NEWID()))
Think you know the answer? Click here, and find out if you are right.
We keep track of your score to give you bragging rights against your peers.
This question is worth
2 points in this category: T-SQL.
We'd love to give you credit for your own question and answer.
To submit a QOD, simply log in to the
Expert Performance Indexing for SQL Server 2012
Expert Performance Indexing for SQL Server 2012 is a deep dive into perhaps the single-most important facet of good performance: indexes, and how to best use them. The book begins in the shallow waters with explanations of the types of indexes and how they are stored in databases. Moving deeper into the topic, and further into the book, you will look at the statistics that are accumulated both by indexes and on indexes. All of this will help you progress towards properly achieving your database performance goals.
This nifty little script has bailed me out on a couple of occasions. It's really quite simple and I will definitely admit it probably could be "fixed" up a whole lot, but it does work as-is (but you will need to change the send mail section at the end).
At our company we tend to work a lot with Transaction Replication and often when we've had to take new snapshots of our tables, we lose all of the non clustered indexes that were specifically used for reporting on the tables that were previously replicated. I wrote these scripts (partial snippets taken from various sites across the net) to assist in recreating those indexes, either from issues with replication, accidental deletion/change, or just to feel safe knowing I had their definitions stored somehwere!
The last script will basically loop through the entire server/database your specify and create the indexes for you, sending you an email for each failed index that fails to get created.
The first script creates a table to store the indexes.
The second script creates the SQL Agent Job. You can eitherpaste the main segment of code directly into the job step where it says "INSERT CODE FROM ABOVE INTO THIS JOB STEP", or create a stored-procedure, and use that instead.
Deploy the job/procedure to any server you wish to keep back up your index definitions, setting an appropriate schedule for it to run.
Use the final portion of code to loop through the table created in step 1, to automagically create the indexes on the target server.
How to login using sqlcmd
my rdbms version :2012 sqlexpress
I created the login using the below commands:
IF EXISTS( SELECT * FROM sysdatabases WHERE name='permissionsDB' )
it's a bug?
- Hello guys,
I've this command:
Select db_name(DB_ID()) as DBName,SS.name as SchemaName,SO.name as TableName, SI.name as Indexname,index_type_desc as IndexType ,avg_fragmentation_in_percent as FragmentationPercentage, (case...
Need Help on query
create table sample ( a date,b date, c date ,d date )
insert into sample values (null,GETDATE(),GETDATE(),GETDATE())
insert into sample values (null,GETDATE(),GETDATE(),null)
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.