Viewing 15 posts - 5,251 through 5,265 (of 59,089 total)
Hi,
You can use the undocumented function sys.fn_dblog() to identify the insert time from the transaction log.
Please refer to the following link for more details.
https://dba.stackexchange.com/questions/189485/how-can-i-find-time-of-an-insertion#:~:text=2%20Answers&text=You%20can%20find%20INSERT%20time,name)%20in%20the%20result%20set.
Thanks.
It'll be interesting to try to...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 23, 2021 at 2:24 am
First of all, if missing a single T-Log backup causes the T-Logs to grow too large, then you folks need to sit down and come up with some extra space...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2021 at 3:08 pm
This is how I solved the issue:
use InputDatabase;
run my scripts where my inserts look like this:
insert into OutputDatabase.Scheme.Table
I still don't understand why it matters so much if the current...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2021 at 2:45 am
Hi,
I have to import csv files with hundreds of columns and only few thousands of records. The flat file import wizard does not do full sampling and may identify...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2021 at 1:11 am
Thank you Phil.
Would it be advisable to do it in SQL server itself, as we have some senior management they opted to use SQL server only (son interms of...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 22, 2021 at 12:54 am
Really helpful in understanding the topic.The content is good and understandable.
Awesome!. What did you actually like about "the content" and how was it "really helpful"?
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2021 at 2:02 pm
Large amount of email recipients (> 5000 per row). Final count of split values was ~73 million records
Been there and done that in the past! Thank you for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 21, 2021 at 1:56 pm
I'[m always curious... what is the data in the VARCHAR(MAX) column that is being split? Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2021 at 11:27 pm
One easy way to find out if autostats is the culprit is to... temporarily turn it off. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2021 at 9:00 pm
Having a quick look at what you attached, here's what I would do...
I'd lay out a staging table with the correct columns with the correct datatypes.
I'd then setup to do...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2021 at 8:55 pm
There are actually a couple of compounding problems with the code... and it's not because of the code... it's because of the stupid stuff MS has done.
First, there's a problem...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2021 at 7:21 pm
Awesome! Thanks for the update!
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2021 at 7:12 pm
Heh... I absolutely love it, Sergiy. +1 billion!
--Jeff Moden
Change is inevitable... Change for the better is not.
May 20, 2021 at 12:18 pm
I am not sure why you marked the previous answer as spam ...
It may be that no one marked the post as SPAM. It may have been the automatic...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 18, 2021 at 6:37 pm
Thank you Jeff,
The target table is to be used for only one processing and won't be used by any other users at all. it's like a collection bucket.
That's why...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 17, 2021 at 12:58 pm
Viewing 15 posts - 5,251 through 5,265 (of 59,089 total)