Issue with Data Load about ds3

[dmorse76]

When you're installing SQL, make sure you add Full Text Search:
https://www.mssqltips.com/sqlservertip/6841/add-full-text-search-sql-server/

[ajayvaaka]

It worked,Can you help me with next step .

I tried using server ip /server name that i'm working with .

Thanks & Regards
Ajay Vaaka

[dmorse76]

When you run the driver without any parameters, it will tell you "Enter parameters with format --parm_name=parm_value"

So, change all your single "-" to "--"

[ajayvaaka]

Thanks for correcting it. still no luck

[ajayvaaka]

10.1.11.6 is there serverwhere i'm working ( win 2019; sql :2019)

[dmorse76]

The error you're getting is "Login failed for user ds3user".

It looks like the Heraflux guide you followed has some outdated instructions, specifically the part where it says "Do a find and replace in the entire file and replace ds3user with ds2user, as this is a holdover from the previous version of the benchmarking tool." You'll need to skip that part of the guide and re-do everything, then it should work.

The ds2user -> ds3user bug was fixed back in 2017, so that Heraflux article should be updated. I'll reach out to David Klee and let him know.

[toddmuirhead]

Error indicates that the ds3user login failed. This probably means that it wasn't successfully created when you ran the sqlserverds35_create_all.bat script for the database. Not sure why it would have failed, but you can run just the user creation step from ds35/sqlserverds35/build/sqlserverds35_create_user.sql script.

David's comment came in while I was writing the above response. Probably a better idea to re-run the whole create-all script as he recommends to make sure that everything is done correctly and it completes without errors. If you to try just rerunning the create user script you might not be as sucessful.

David - Thanks for responding to this issue.

[ajayvaaka]

ds35/sqlserverds35/build/sqlserverds35_create_user.sql : Ran successfully
didn't changed this time ds2user -> ds3user ; load successfully

Test result is same

tried both ds3 & ds35

[dmorse76]

Make sure you have TCP/IP enabled for your SQL Server instance: https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/enable-or-disable-a-server-network-protocol?view=sql-server-ver15#SSMSProcedure

[ajayvaaka]

observed it is enabled already . just disabled->re-enabled and started services . After that also no-luck

[dmorse76]

Maybe it is a firewall or some other networking issue. To rule that out, you could try copying ds3sqlserverdriver.exe directly to the SQL Server machine itself and run the driver directly it by specifying --target=localhost

[ajayvaaka]

i'm running on localhost , where SQL is running .

Thanks & Regards
Ajay Vaaka

[toddmuirhead]

Login to the sql server managment studio as administrator and see if ds3user exists as a user under Security -> Logins. If it does exist, delete it and rerun the script. Now, can you logon as user ds3user to sql server via the sql server management studio?

If this is successful, then the user is there and the error is being caused by something else. Try running the ds3sqlserverdriver.exe with just the target, db_size, and n_threads parameters.

If you still can't get it to work, maybe we can do a zoom call on Monday and interactively figure out what it going on.

Thanks - Todd

[ajayvaaka]

Login to the sql server managment studio as administrator and see if ds3user exists as a user under Security -> Logins. If it does exist, delete it and rerun the script. Now, can you logon as user ds3user to sql server via the sql server management studio?

• i able to see ds3user and remove it and re-ran script . I can't login with ds3user . I'm taking guidence from my SQL team. will keep you posted after that. i belive ds3user password is empty ( that is how i'm trying)

[ajayvaaka]

i'm able to communicate now.

Can you guide me next step please. is this look accurate ?

Thanks & Regards
Ajay Vaaka

[toddmuirhead]

This message means that the Login1 stored procedure that is the first one called with DS 3.5 does not exist. If you built the DS 3 version of the database, then you need to use the ds3 driver instead of the 3.5 version that you are using here. If you did creat the 3.5 version, then the rest of the stored procedures probably also were not created. I would bet that other parts didn't create successfully either. Rerun the create all script and save all of the screen output. If it doesn't work after rerunning the create all script, send me the output. What was the issue that was preventing it from connecting that you fixed? Thanks, Todd

…

On Mon, May 2, 2022, 6:34 PM ajayvaaka ***@***.***> wrote: i'm able to communicate now. [image: image] <https://user-images.githubusercontent.com/17277729/166342518-9d5bb5a4-e35a-4026-b2fd-d921dd8a05a0.png> Can you guide me next step. is this look accurate ? Thanks & Regards Ajay Vaaka — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABZ36KV24EFHTFG3WFDUWR3VIBQ7BANCNFSM5UW6X2HA> . You are receiving this because you commented.Message ID: ***@***.***>

[ajayvaaka]

Thanks Todd for huge help.

Worked after using ds3 driver

What was the issue that was preventing it from connecting that you fixed?

• SQL mixed mode
• previouly , i can't able to connect to SQL using ds3user . i make sure it worked .

Thanks & Regards
Ajay Vaaka