On 2/5/25 14:58, Andy Hartman wrote:
Reduce batch size still caused error as reported nothing in WIndows
Server log...
The SimplySql is slick because just qry from src and load to dst ...
Is there any way to somehow show more of the error in PS i tried the
$error but nothing very descriptiv
This is going to be a monthly process not just a 1 time exercise.
On Wed, Feb 5, 2025 at 5:58 PM Andy Hartman wrote:
> Reduce batch size still caused error as reported nothing in WIndows Server
> log...
>
> The SimplySql is slick because just qry from src and load to dst ... Is
> there any way
Reduce batch size still caused error as reported nothing in WIndows Server
log...
The SimplySql is slick because just qry from src and load to dst ... Is
there any way to somehow show more of the error in PS i tried the $error
but nothing very descriptive
On Wed, Feb 5, 2025 at 4:23 PM Adrian Kl
On 2/5/25 13:05, Andy Hartman wrote:
nothing in log from mssql side and no anti-virus
How about the Windows Server 2019 system log?
--
Adrian Klaver
adrian.kla...@aklaver.com
On 2/5/25 13:09, Andy Hartman wrote:
I also reduced batch size to 5000 on the last run .. I like using this
SImplySql because it's a script I can launch, so that's why I chose that
solution... I'm using it to load a History Env.
You really need to complete your thoughts, remember we have no
Could there have been a network hiccup? Or some sort of timeout?
If I needed to transfer 360GB of data, I'd probably do something old school
like:
1. write a PowerShell script to export a set of rows into a csv file, 7zip
compress it, then rsync or scp it to the target.
2. Write a bash script to
I also reduced batch size to 5000 on the last run .. I like using this
SImplySql because it's a script I can launch, so that's why I chose that
solution... I'm using it to load a History Env.
THanks again.
On Wed, Feb 5, 2025 at 4:05 PM Andy Hartman wrote:
> nothing in log from mssql side and
nothing in log from mssql side and no anti-virus
On Wed, Feb 5, 2025 at 2:06 PM Adrian Klaver
wrote:
>
>
> On 2/5/25 9:46 AM, Andy Hartman wrote:
> > [6992] ERROR: unexpected EOF on client connection with an open
> transaction
> > 2025-02-05 12:19:44.919 EST [6992] CONTEXT: COPY sqlt_data_1_2
On 2/5/25 9:46 AM, Andy Hartman wrote:
[6992] ERROR: unexpected EOF on client connection with an open transaction
2025-02-05 12:19:44.919 EST [6992] CONTEXT: COPY sqlt_data_1_2022_03,
line 24431524, column dataintegrity
2025-02-05 12:19:44.919 EST [6992] STATEMENT: COPY sqlt_data_1_2022_03
[6992] ERROR: unexpected EOF on client connection with an open transaction
2025-02-05 12:19:44.919 EST [6992] CONTEXT: COPY sqlt_data_1_2022_03, line
24431524, column dataintegrity
2025-02-05 12:19:44.919 EST [6992] STATEMENT: COPY sqlt_data_1_2022_03
(tagid, intvalue, floatvalue, stringvalue, d
On 2/5/25 05:40, Andy Hartman wrote:
mssql - 2016
PG - 16.1
latest release for Simplysql
Latest is a relative term and requires anyone in the future coming
across this thread to work out what you are talking about. For that
person the current version is 2.1.0.
Invoke-SqlBulkCopy -SourceConnec
mssql - 2016
PG - 16.1
latest release for Simplysql
Invoke-SqlBulkCopy -SourceConnectionName "src" -SourceTable
"sqlt_data_1_2022_03" -DestinationConnectionName "dst" -DestinationTable
"sqlt_data_1_2022_03" -BatchSize 1 -Notify
2.4 billion records -- I have down other tables of same size no p
On 2/4/25 11:51 AM, Andy Hartman wrote:
I'm copying a large table from mssql to PG using SImplysql and in the
Log I see this message
2025-02-04 14:42:17.975 EST [4796] ERROR: unexpected EOF on client
connection with an open transaction
The above pretty much spells it out.
Something mess
I'm copying a large table from mssql to PG using SImplysql and in the Log I
see this message
2025-02-04 14:42:17.975 EST [4796] ERROR: unexpected EOF on client
connection with an open transaction
2025-02-04 14:42:17.975 EST [4796] CONTEXT: COPY sqlt_data_1_2022_03, line
208274199, column tagid
2
14 matches
Mail list logo
