How using DB Tool ?

[Vanderleck16]

Hi,

I am trying to manage differents datas streams and I am stuck at the step of saving data to a database.
Unfortunately, I 'm having trouble using the database tools in alteryx.
For example, I would like to save data in a database, in a specific schema.

So I used the  Data Stream IN tool to transform the data into a database, then I choose the Selection tool to keep on the fields that I want and finally I save the data in the database with the Write Data in DB tool.

But, I don't know where I can specify the exact path where the data should register, for example I would like to create a table in the following path:
Database = Sales
from users.here_to_create_new_table.

Another thing, I would like to know if it was possible to use alteryx as a data management tool. Rather than making queries in SQL Server, to delete a table, create, rename ... use alteryx directly but without necessarily having an input file.

Thank you for the help.

[MattBSlalom]

To answer both of your questions, we first need to clarify that the "In-Database" tool palette are tools to push the data processing down into the connected database engine rather than pulling all the data into Alteryx's memory for processing.  Behind the scenes, a collection of "In-Database" tools will generate a SQL query that is passed over to the database to be executed.

For your first question, it sounds like the source of your data may not be coming from the database so your initial tools are the standard In/Out, Preparation, etc.  If that's the case, you should use the standard Output Data tool from the In/Out palette (not the Write Data In-DB tool from the In-Database palette).  The standard Input Data tool and the standard Output Data tool can both connect to database platforms.  The Output Data tool should allow you to specify the connection information to your database as well as the target schema & table.

The answer to your 2nd question about using Alteryx as a "data management tool", is yes, it's possible.  Depending on what tasks you want to accomplish, it may be very cumbersome or very simple.  Typical ETL scenarios of moving data from one table to the next, is very well suited to those In-Database tools (assuming source & target are accessible from a single connection).  Your source data could come from a Connect In-DB tool rather than an Input Data tool.  As far as more DBA / database maintenance tasks, Alteryx is not really an ideal tool.