Complaining and explaining are not the same things.

Complaining and explaining are not the same things. You can explain a horrible situation without complaining. If you do that, most of the time, it means you want to solve a situation. Now, here comes the question. In your company, when you gather people together, do they complain or explain the difficult situations they are going through? Complaining doesn't help. It is just an exhausting habit for you and for everybody around you. Every complaint is praying to the devil - Bob Marley.

Why daily meetings do not encourage the habit of documenting.

Why daily meetings do not encourage the habit of documenting. Very simple. Unless the company has a department focused on documentation, daily meetings make people talk (a lot, depending on your country). When people talk, subconsciously they think that what they know is already known by everybody. So, "Why documenting, if everybody knows what I know. After all, we talk every day. It's impossible that he or she isn't aware of what I'm doing, right?" It's a tricky situation. Daily meetings pass two messages. A clear one is that everybody must be "on the same page", and another hidden one "Don't worry. We already talked. You don't need to write anything"

SELECT failed because the following SET options have incorrect settings: 'ARITHABORT'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations.

SELECT failed because the following SET options have incorrect settings: 'ARITHABORT'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations.

This problem was happening whatever I tried to execute a stored procedure.
My solution was

At the beginning of the stored procedure I wrote

CREATE PROC [dbo].[YourProc]
    @yourparameter varchar(50)
AS
BEGIN

    SET ARITHABORT ON

WINRAR.exe zip - How to zip de files and subfolders

a -afzip -r -ep1  "path\file.zip"  "path\directory you want to zip\"

Don't forget the last left slash.
Do the test with and without the left slash and you'll see the subtleness.

:)

How to cause a deadlock on SQL Server on purpose

Hi!

What I really needed was an error with the word deadlock inside of the message, so this is what I did.
Whenever I need a deadlock to raise up I execute my procedure proc_deadlock.
Then I make my code treatment based on the message that contains the word deadlock.


USE [master]
GO

/****** Object:  StoredProcedure [dbo].[proc_deadlock]    Script Date: 25/04/2018 12:47:19 ******/
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

create procedure [dbo].[proc_deadlock]
as

    -- RAISERROR with severity 11-19 will cause execution to 
    -- jump to the CATCH block. 
    RAISERROR ('this is my deadlock', -- Message text. 
               16, -- Severity. 
               1 -- State. 
               ); 

GO

Demonstração Power BI - 2

Project to test classifications

http://itclassified.herokuapp.com/itclassified/