Restrict a Batch user access from SQL Assistant - teradata

Could you please guide me how to restrict a Batch user access only from SQL Assistant. I am using Teradata Version 17. Thanks in advance.
Regards,
Umair
Restrict a Batch user access only from SQL Assistant

This could be your restriction filter:
select * from Dbc.sessionInfo
where
LogonSource like '% SQLA %'

Related

what is a great progress query tool

I am new to Progress. Previously I worked with Oracle, MSSQL and MYSQL. What is a great progress query tool, free or paid? I want to be able to write simple SQL queries.
In oracle i am using Toad,Pl/sql developer tool to connect oracle. Any thing in Progress 4gl?
Thank you
You can use any random SQL query tool that you like if the SQL engine has been exposed by the DBA. You just need login credentials and permissions just as you would for any SQL db.
Since you want to write SQL queries you should be looking for SQL access not 4GL tools. There is a very, very limited SQL subset embedded within the 4GL but that was created in the 80s and is little more than a marketing gimmick. For anything but trivial SQL you want to use the SQL-92 engine. Which means the DBA needs to have started a SQL broker, provided a port # for you and has granted appropriate permissions.

Connection to Virtuoso Database with sparqlib PHP

I am using PHP to connect to endpoint to Virtuoso.
I have found SPARQL library and I have made some queries. The problem is that if I insert a huge string, Virtuoso doesn't allow me. When I do this query from Conductor, it is inserted. So I want to connect to database through sparqlib and insert my username and password. I haven't found anything like this. Is it possible?

OpenEdge SQL DBA Account Setup

I'm setting up SQL access in a newly created OpenEdge 11.5 database.
In checking the contents of the sysdbauth table using "select * from sysprogress.sysdbauth", I see that there are two users setup by default: sysprogress and a user with the name of the Linux user account that was used to create the database.
I'm looking for recommendations as to how to handle these two accounts. Obviously I want to have an account to use for DBA tasks. Should I use one of these accounts for the purpose? If so, what should I do with the other account?
Is it possible (and safe) to be deleting either of these predefined accounts?
On page 175 of the Database Administration guide you can read about default users and why they are created:
Tables used from SQL only
An SQL database administrator (DBA) is a person assigned a sysdbauth record in the database.
SQL DBAs have access to all meta data and data in the database. To support internal schema
caching, every OpenEdge database begins with a DBA defined as "sysprogress." However,
OpenEdge restricts the use of "sysprogress."
When you create an OpenEdge database using the PROCOPY or PRODB commands, and the
database does not have any _User records defined (from the source database, for example), then
a DBA is automatically designated with the login ID of the person who creates the database. This
person can log into the database and use the GRANT statement to designate additional SQL DBAs,
and use the CREATE USER and DROP USER statements to add and delete user IDs.When creating
users, this DBA can also specify users as SQL-only users, who can only access the database
through SQL.
There are several knowledge base entries around the task of deleting or disabling the default users.
http://knowledgebase.progress.com/articles/Article/P5094
http://knowledgebase.progress.com/articles/Article/P161411
This suggests that it's really safe to delete or disable these accounts but you should:
1) Create replacing accounts first.
2) As always: test in a separate environment first and not in production!
Yes, in fact Progress kind of expects you to do so. Create a root account and get rid of both. It's fine.

How to stop sql assistant?

I have run a query in teradata and sql assistant in (Not Responding)
I do not want to loose the query?
What can I do to stop it and keep the query
Open another instance of SQL Assistant and see if the query has been saved to the History.
Ask the DBA to abort your session on your behalf which should return control to SQL Assistant.
Ask the DBA if DBQL has been enabled and how you can retrieve the SQL from the query logs. (You may or may not have direct access to the logging tables.)

Can a non dba user create oracle job?

Hi i have connected to oracle as a non dba user (ie, it has no 'dba' privilege).I tried to create an oracle JOB with this user.
But I couldn't. Is it possible to do it as a non dba user?
(Also ,before creating the Job i tried to get what's the current maximum id of existing JOBs.That also I couldn't)
You don't need DBA privileges to creae a job.
For further details check the Security Model chapter in the Oracle documentation:
DBMS_JOBS
DBMS_SCHEDULER

Resources