Either one can do the install.  The DBA will need to provide some settings for the Windows team, but that team should be able to do an install as well.

No.

If it's doing a lookup only (not modifying data, just reading it), you could also use WITH (NOLOCK) on the table to reduce overhead of the lookups.  I would argue...

View sys.change_tracking_databases returns the db names of all dbs that have change tracking enabled.

Thus, the db name will not be in the view if change tracking is off.

            
August 17, 2021 at 1:51 am
            
#3920565

            
            
                                                
        

You could do some major clean up on your existing code:

1. Don't use nvarchar unless you absolutely must have it, use varchar instead.

2. Don't use (MAX) unless you absolutely must...

There are only two processes involved in the deadlock.

Make sure you have an index on

dvd ( bed_id, wns_id, dvb_id )

Actually, all these tables should almost certainly be clustered first on bed_id,...

...

N'<th>Count of Records Successfully Uploaded Today: </th></tr>' +

-- Below is the query of which the results are passed into the rectangle

CAST((SELECT COUNT(*) FROM .[dbo].[Stage_SMSLog]

with (NOLOCK) WHERE datestamp = CONVERT(nvarchar(10), GetDate(),120))...

You need format 120 rather than 20: 20 will leave off the century, so you'd get 21 for yy instead of 2021, therefore it won't match.

A trigger would be more consistent than using a proc, unless you only want to do this for certain, specific INSERTs:

USE tempdb;

IF OBJECT_ID('dbo.FirstTable') IS NOT NULL
 ...

AT TIME ZONE clause.

I think Google has some type of API that does address correcting.

I'd look for that or some other known app to do this.  What you're trying to do is way...

Yeah, we can't anything to improve things without seeing that code.

DECLARE @first_sales_month date = '20200101'
DECLARE @last_sales_month date  = '20201201'

SET @first_sales_month = DATEADD(MONTH, DATEDIFF(MONTH, 0, @first_sales_month, 0)
SET @last_sales_month = DATEADD(MONTH, DATEDIFF(MONTH, 0, @last_sales_month, 0)

SELECT
   ...

I suggest you always explicitly set XACT_ABORT, either ON or OFF.  After that, you just need to understand the implications of  the XACT_ABORT setting.

If it's OFF, you may have parts...

SQL creates a table entry for all db backups.

Look in table "msdb.dbo.backupset" to find the lastest full backup datetime for each db, and link to table "msdb.dbo.backupsetfamily" to find the...

You'd want to make sure PAGE compression was actually appropriate for each specific table first.  In certain cases, page compression doesn't do enough good to make it worth SQL's effort...