Yes I know...I also know that he, the author, put a comment to make the table creation an option. So telling it that it doesn't do it the way I want seems pointless.
Although I will tell him that the documenation should definitely state this.
Unless something has changed since I last worked on that node, the table will only be created if it does not exist. If the table exists then it will be used. That was the intention of the feature.
The .create = true flag was set true until it could be later exposed. Not because it could be used to "bulk full an existing table" but to "throw an error if the table doesn't exist". The difference is subtle but meaningful.
TIP: If you set table.create to true, module will check if the table exists before it start sending data. If it doesn't, it will automatically create it. You can specify primary key columns by setting primary: true to column's options. Primary key constraint on multiple columns is supported.
I don't know anything about mssql, but if it is doing a 'create table if not exists' then perhaps you need create permissions even if it doesn't actually end up creating the database.
Was it creating a new table if it already existed, or was it just that it needed the permissions in case it had to?
Did the user have ADMINISTER BULK OPERATIONS permission?