Viewing 15 posts - 2,326 through 2,340 (of 22,224 total)
Stored procs are fine. Great way to exercise MORE control and avoid all the issues we've listed with joining and nesting views. I don't object to using stored procs. I...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2019 at 3:03 pm
Also, which would be preferable for report sources -- UDF or stored proc?
Not a comparison I would make. They do different things and will have different uses. Stored procedures...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2019 at 2:47 pm
Same issue on the differentials. If you run a restore and allow recovery, you can't apply a differential.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2019 at 12:11 pm
On the reset, I mean re-restore. To do the log shipping, you can't have recovered the database. It has to be left in recovery. If you already recovered the database,...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2019 at 12:10 pm
Some good info, let me add a couple of more wrinkles.
First, an inline UDF has a nickname, a parameterized view. It's way to set up a query, with parameters, to...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2019 at 12:05 pm
It is an interesting question. I suppose if there were zero data changes, you probably could just restore the index in a piecemeal restore if it's on a different file...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2019 at 11:58 am
As you've defined it, can you just capture the delta? No.
Instead, you have to look at additional processes or methods to arrive at this. For modern servers, I recommend looking...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2019 at 11:45 am
If you're rebuilding all the indexes, stats are not a worry. However, since you're doing a bunch of partial updates, I'd be a bit more concerned that simply enabling indexes...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 29, 2019 at 11:27 am
This is why we should comment our source code and version control checkins - so those who follow us can better understand why we did things...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 28, 2019 at 3:51 pm
This is why we should comment our source code and version control checkins - so those who follow us can better understand why we did things the way we...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 28, 2019 at 1:50 pm
erm…. I picked up on one word - "weekend"
so is there any possibility that it's a rebuild index with "Sort in tempdb" option enabled... we all know which jobs...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 28, 2019 at 1:45 pm
Sounds like you're probably OK. Update the statistics after a data load like this.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 28, 2019 at 11:29 am
This is flat out a coding and design issue. The code could be simply bad. Or, it could be doing things that aren't using the appropriate data structures, indexes, etc.....
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 28, 2019 at 11:29 am
Sub queries come in several stripes. Correlated sub-queries (which I shy away from)
SELECT
(SELECT b.cola FROM tableb AS b
WHERE b.ID = a.id)
FROM tablea AS a
WHERE a.otherid = 42;
Or, as a table...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 9, 2019 at 11:43 am
Create specific logins as owners for the databases. Just as in the other question you asked, least privilege principle should always apply. Setting 'sa' as owner potentially opens things up...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
October 9, 2019 at 11:36 am
Viewing 15 posts - 2,326 through 2,340 (of 22,224 total)