Viewing 15 posts - 22,261 through 22,275 (of 59,098 total)
Got it. Working on it.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2014 at 9:53 pm
Yes. I'm curious though... why isn't the full path a file name contained in the table? Without esoteric controls, you wouldn't be able to work your way back...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2014 at 7:59 pm
This would be super simple to do if you were allowed to use xp_CmdShell. Can we do that or do we need to avoid it?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2014 at 7:36 pm
Can we see that separate code that works for one image, please?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2014 at 6:47 pm
PearlJammer1 (12/8/2014)
This is a question from a high level view about the possibility of removing a cursor from some of our tsql code.
Basically the steps are:
We create a temporary...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2014 at 6:34 pm
Eirikur Eiriksson (12/8/2014)
Quick joke, 36524 is the number of versions Jeff needs to upgrade on his old test box 😀😎
Heh... better joke... that's the number of times I've heard that...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2014 at 4:46 pm
jshahan (12/8/2014)
select CAST(RAND(CHECKSUM(NEWID()))*3653.0+36524.0 AS DATETIME)
Not difficult to see WHAT is happening but WHY are these particular constant...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2014 at 4:44 pm
You still need to find out about RPO, RTO, and what the Restore Plan is, though. While 380GB isn't a "HUGE" database, it can take a fair amount of...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 8, 2014 at 10:24 am
mike 57299 (12/7/2014)
Facts:
Full recovery model
Mirrored to 2nd SQL server
full backup taken every morning...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2014 at 2:02 pm
This should do it and it will be SARGable...
--===== These would be parameters for a stored procedure.
DECLARE @pStartMonthDate DATETIME --Can be any date in the starting month
...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2014 at 1:37 pm
Eirikur Eiriksson (12/7/2014)
Quick suggestion😎
SELECTPT.idx
,PT.paymentDte
,PT.officialReceiptNo
,PT.sysReceiptNo
FROM dbo.paymentTrnx PT
WHERE (YEAR(PT.paymentDte) * 100) + MONTH(PT.paymentDte) BETWEEN 201201 AND 201203;
Careful...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 7, 2014 at 1:15 pm
So what does the rest of the insert statement look like and what is the error that you're getting? If it's an actual error, please post the actual error...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2014 at 10:38 pm
You have to remember that EVERY column is a part of the leaf level of the clustered index or a part of the heap. If you added data to...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2014 at 10:35 pm
MyDoggieJessie (12/6/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2014 at 12:48 pm
Great article, Phil. Thanks for taking the time to write it.
Having been both an FTE that had to fix legacy systems and a consult that's had to do the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 6, 2014 at 12:44 pm
Viewing 15 posts - 22,261 through 22,275 (of 59,098 total)