Most of us that are data professionals think the best way to make decisions is to use data to justify some course of action. We look for patterns in data, some guidance that the information we have will lead us to make the best choice for our organization. Google has talked about making data driven decisions as a part of their success and they think more organizations should do this. Any number of other companies also use data to power their BI systems and dashboards that help their employees make better choices.
That seems in contrast to this piece from the Harvard Business Review that says that great decisions don't start with data. It talks about using stories and emotions, with a few key facts sprinkled in, to help sell ideas and get decisions made. On one hand I agree that stories help to sell decisions, but I often have found that successful salespeople use this technique to deceive and convince by plucking emotional heartstrings, and using relatively little data.
In my mind, the best way to make decisions is to go with your instincts, but while examining and understanding the data. You can't discard data, especially when it presents strong patterns. However data can be deceiving when we don't carefully examine the ways in which it's put together. An average doesn't always reflect the actual value of a set of numbers, especially when we don't also understand the range, standard deviation, and count of values.
We also have to realize where we do and don't have experience and expertise in some subject. We should certainly look to data to guide us and perhaps even justify our decisions, but we can't forget that the human brain is still an important part of any computational exercise. We need employees that you use their judgement, in collaboration with data, to make the best decision for our organizations.
Many DBAs back up their user databases, but not their system databases. Whatever the reason for the lack of a backup, John Grover explains how to save yourself (mostly) should you ever find yourself with no viable master database and no good backup. More »
Red Gate’s running a half-day training workshop at their UK head office in Cambridge on Aug 8. It’ll show you how to link your database source control repository to your build system as the starting point for continuous integration. More »
When a SQL Server database is operating smoothly and performing well, there is no need to be particularly aware of the transaction log, beyond ensuring that every database has an appropriate backup regime and restore plan in place. When things go wrong, however, a DBA's reputation depends on a deeper understanding of the transaction log, both what it does, and how it works. An effective response to a crisis requires rapid decisions based on understanding its role in ensuring data integrity.
COUNT(*) AS Result
ON UNICODE(CAST(d1.name AS VARCHAR(255)) COLLATE Latin1_General_CS_AS) = UNICODE(CAST(d2.name AS NVARCHAR(255)) COLLATE SQL_Latin1_General_CP850_BIN)
d1.database_id <= 4
AND d2.database_id <= 4;
Cannot resolve the collation conflict between "SQL_Latin1_General_CP850_BIN" and "Latin1_General_CS_AS" in the equal to operation.
This is incorrect because we are specifying a collation for a string before passing the string to the UNICODE function and then comparing the output of the function which is an integer. We would receive this error if we were comparing the strings.
This is a red herring. Although the function only returns the unicode value for 1 character, the function will return the value for the first character of the input expression. The casting of the two values differently doesn't matter because the input expression is a ncharacter expression and the input values will be converted implicitly.
Anyone who is using this script can schedule this on 1st of every month for moving full backup file from source to destination location. The name of the source file is considered as "2014_05_31". You can change the source format according to your needs.
Redbuild CMS tables from XML file
I had to reinstall my local copy of SQL a few weeks ago, which naturally overwrote the msdb.dbo.sysmanagement_shared_server_groups_internal and msdb.dbo.sysmanagement_shared_registered_servers_internal...
Unable to create credentials
- What is the needed permission to create credential except for sysadmin?
Already granted securityadmin but still user does not have permission...
if where on update doesn't match do an insert
I have this
SET OrthoID = '@Request.inpHidden~'
WHERE BankID = SUBSTRING('@Request.TransDesc~', 0, 25)
I wish to add, if there isn't a match...
Difference in Time for same query
- Query time having different timings
[code="plain"][b]Start Time End Time[/b]
2014-07-23 12:10:28.423 2014-07-23 12:10:28.643
Select col1,col5,col8,col9,col10,col12,col14,col15,col16,col17,col18,col19,col20 from Table_name
[code="plain"][b]Start Time End Time[/b]
2014-07-23 12:10:28.657 2014-07-23 12:10:30.860
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.