July 27, 2017 at 2:07 pm
Hello,
We’ve got a weird thing happening and I wanted to run it past you for thoughts and ideas. We have several times a day, an Attunity provider/Teradata driver connection to Teradata, where we execute a Select statement query to extract data to the SQL Server been running about 1.5 years now.
We only extract data and its always done via a query with a select, we do not CREATE/REPLACE tables or views or exec procs, etc So I get notified by a Teredata DBA telling us that about 100 times day, for quite some time, our Logon ID used by the SQL Server fails to create views due to lack of privileges.
We are not creating views, and when he gave us a sample script, we are now thinking that there some background service that SQL Server may be doing like creating a temp dynamic DateNamed view when it connects to pull that data through, then dissolves when completed.
Views it created in code that he gave us that we did not code into the SSIS package: CREATE VIEW SSIS_20170726122537_994 AS ( Sel…
Please let me know if my hunch is right, and what we can do about that, or, if Teradata is going to need to learn how to deal with the ID needing to create the temp view from SQL Server.
Thanks,
JPQ
July 27, 2017 at 2:31 pm
quinn.jay - Thursday, July 27, 2017 2:07 PMHello,We’ve got a weird thing happening and I wanted to run it past you for thoughts and ideas. We have several times a day, an Attunity provider/Teradata driver connection to Teradata, where we execute a Select statement query to extract data to the SQL Server been running about 1.5 years now.
We only extract data and its always done via a query with a select, we do not CREATE/REPLACE tables or views or exec procs, etc So I get notified by a Teredata DBA telling us that about 100 times day, for quite some time, our Logon ID used by the SQL Server fails to create views due to lack of privileges.
We are not creating views, and when he gave us a sample script, we are now thinking that there some background service that SQL Server may be doing like creating a temp dynamic DateNamed view when it connects to pull that data through, then dissolves when completed.
Views it created in code that he gave us that we did not code into the SSIS package: CREATE VIEW SSIS_20170726122537_994 AS ( Sel…
Please let me know if my hunch is right, and what we can do about that, or, if Teradata is going to need to learn how to deal with the ID needing to create the temp view from SQL Server.
Thanks,
JPQ
I would be very surprised if SSIS were doing this. It's more likely that either
a) The driver is doing it, or
b) That this is how Teradata reacts when it receives these requests via the driver.
Is this something which has always happened, or something which started happening a while ago, for no apparent reason?
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
July 27, 2017 at 2:34 pm
Phil Parkin - Thursday, July 27, 2017 2:31 PMquinn.jay - Thursday, July 27, 2017 2:07 PMHello,We’ve got a weird thing happening and I wanted to run it past you for thoughts and ideas. We have several times a day, an Attunity provider/Teradata driver connection to Teradata, where we execute a Select statement query to extract data to the SQL Server been running about 1.5 years now.
We only extract data and its always done via a query with a select, we do not CREATE/REPLACE tables or views or exec procs, etc So I get notified by a Teredata DBA telling us that about 100 times day, for quite some time, our Logon ID used by the SQL Server fails to create views due to lack of privileges.
We are not creating views, and when he gave us a sample script, we are now thinking that there some background service that SQL Server may be doing like creating a temp dynamic DateNamed view when it connects to pull that data through, then dissolves when completed.
Views it created in code that he gave us that we did not code into the SSIS package: CREATE VIEW SSIS_20170726122537_994 AS ( Sel…
Please let me know if my hunch is right, and what we can do about that, or, if Teradata is going to need to learn how to deal with the ID needing to create the temp view from SQL Server.
Thanks,
JPQI would be very surprised if SSIS were doing this. It's more likely that either
a) The driver is doing it, or
b) That this is how Teradata reacts when it receives these requests via the driver.
Is this something which has always happened, or something which started happening a while ago, for no apparent reason?
Apparently it's been happening a very long time, and unbeknownst to us, we receive no errors and have no issues with the packages running the extracts
July 28, 2017 at 6:03 am
If you run the same query from, say, Access, (using the same driver) is there still an attempt to create the VIEWs?
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
July 28, 2017 at 7:41 am
Phil Parkin - Friday, July 28, 2017 6:03 AMIf you run the same query from, say, Access, (using the same driver) is there still an attempt to create the VIEWs?
Access connecting to Teradata and executing the query does not produce the create view effect it seems to with SSIS and the Attunity
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply