Embed Size (px)
Citation preview
1
© 2015 Teradata
Brian Wood, Director of Cloud Marketing, Teradata
Ray Newell, Learning Consultant, Teradata
Kevin Bogusch, Cloud Marketing, Teradata
Cloud Analytics ExperienceWelcome + Kickoff
© 2016 Teradata
2
2
Welcome!
• Today you will learn:
• How to spin up Teradata in the cloud
• Options for Do-it-yourself and As-a-service
• How to use Teradata Studio for (new) analytics
© 2016 Teradata
3
3
Thank You to Our Sponsors!
© 2016 Teradata
4
4
Advanced Partner Status
• Top strategic partner in APN
• Multiple levels of collaboration
• Heavy investment in training
• >5,100 accreditations
• >140 certifications
• 8 AWS Well-Architected reviews
• Data & Analytics Competency
© 2016 Teradata
5
5
Today’s Agenda
• 0-to-Launch in 5 minutes
• Do-it-yourself: Launch Teradata in the cloud
• Improve performance with software
– Break –
• As-a-service: See and learn about IntelliCloud
• Use Teradata Studio to run and visualize analytics
• See an nPath analytics demonstration
© 2016 Teradata
6
6
Before Jumping In…
© 2016 Teradata
7
7
Why Cloud?
• Accelerate time-to-value• Avoid lengthy procurement process
• Shift to OpEx• Often preferred over CapEx
• Reduce financial risk• Start small, grow only when needed
• Save money• Belief that cloud = cost savings
??
© 2016 Teradata
8
8
Cloud Consumption Option #1
Do-it-yourself Deployment
“I’ll deploy & manage in AWS myself.”
• Benefit: Broad system customization
• Use cases recommended:
• Proofs of Concept
• Test & Development
• Discovery Analytics / Data Labs
© 2016 Teradata
9
9
Standard Cloud Infrastructure
CPU
Memory
Teradata Software
Network Attached Storage
Software
Computeand
Storage
© 2016 Teradata
10
10
Do-it-yourself Footprint (AWS)
Americas International
Brazil, Canada, U.S. Australia, Germany, India, Ireland, Japan, Korea,
Singapore, U.K.
Teradata Software for AWS not yet available in the China, France, or US GovCloud regions.
© 2016 Teradata
11
11
And Now…Your Instructor
Ray Newell• Teradata Learning Consultant
• Teradata Master certification
• AWS Associate Architect certification
© 2016 Teradata
12
12
Cloud Analytics ExperienceDo-it-yourself Deployment of Teradata in AWS
13
13
DIY Deployment on AWS TopicsTeradata in the Cloud
Teradata Database in the AWS Marketplace
Launching the Teradata Database from the AWS Marketplace
Monitoring the Creation of the CloudFormation Stack
Teradata Database Security Group
Connecting to the Teradata Database via Teradata Studio™
Launching Viewpoint from the AWS Marketplace
Connecting and Configuring Viewpoint
Scaling Teradata Database Instances Up or Down
Scaling Teradata Database Instances In and Out
Expanding EBS Storage
Scaling Query Comparison
14
14
Teradata in the Cloud
15
15
DIY Deployment – Introduction
https://www.teradata.com/Products/Cloud/Do-it-yourself-Deployment/AWS
The web site https://www.teradata.com/Products/Cloud/Do-it-yourself-Deployment/AWS is available to provide additional information about deploying Teradata software on your own.
16
16
DIY – License Options There are two paths for using Teradata software on your own with
AWS infrastructure:
Scrolling down, the Intro menu, you will see that you have two options to deploying your own software. On-demand, in which you pay by the hour as you use Teradata software, or BYOL, in which you use a license that you have previously purchased from Teradata. BYOL provides discounts over the on-demand pricing and is the preferred option if you will be running Teradata software for long amounts to time.
17
17
DIY – Documentation
In the Documentation menu, you will have links to various product documentation. The Deployment and Administration Guide contains the detailed steps for deploying Teradata on AWS.
18
18
DIY – Resources
In the Resources links to various other resources such as videos and white papers.
19
19
DIY – Support
In the Support menu, you will have a link to register for Premier Support which is included with Teradata on AWS.
20
20
Teradata Database in the AWS Marketplace
21
21
AWS Marketplace – Teradata
https://aws.amazon.com/marketplace/search/results?searchTerms=“teradata database”
Searching for “teradata database” in the AWS Marketplace will display the various Teradata Database software tier and licensing options you can choose.
For our example, clicking Teradata Database Enterprise link will take you the Product Overview page.
22
22
Product Overview
This is the Product Overview page for the Teradata Database Enterprise. This will give you information about the Teradata Database Enterprise product along with a short video reviewing the benefits.
23
23
Product Overview (cont.)
Scrolling down the Product Overview page will display additional overview information.
Note: the subscription for the Teradata Database Enterprise also includes additional software that can be launched with no additional software costs. They will incur additional AWS EC2 charges and any storage charges.
24
24
Monthly Pricing
Continuing to scroll down will display pricing information. These are the hourly prices for the Teradata software.
Note: AWS infrastructure costs will vary by Region.
25
25
Annual Pricing
Continuing to scroll down will display additional pricing information. These are the Annual prices for the Teradata software.
Note: AWS infrastructure costs will vary by Region.
26
26
Usage
Scrolling further down, after pricing information, usage information will be displayed.
From this page you also get access to documentation regarding the Teradata Database and more specifically Teradata on AWS.
Note that the Getting Started guide will give you information specifically related to the options you will be seeing and the different parameters you will be required to supply when you launch the software via the CloudFormation Template.
27
27
Reviews
The last information on this page will be reviews that have been submitted. After browsing the information from the Product Overview page, you will need to click the Continue to Subscribe button.
28
28
Subscribe
To be able to launch Teradata software in AWS you will first need to create a subscription. To create a subscription, you must first click the Accept Terms button.
29
29
Subscribe (cont.)
After clicking the Accept Terms button, you will need to wait a minute or so while your subscription request is processed.
30
30
Subscribe (cont.)
After a minute or so, you will have a subscription, and the Continue to Configuration button will be activated. You will need to click that button to continue on the Configuration screens.
31
31
Configure the Software
From the configuration screen, you will choose the Software Version and Region from the drop down menus. You can chose from the current 16.20 version or previous versions 16.10 or 15.10.
Note: There is only one Fulfillment Option available.
32
32
Annual License Option
If you choose, it is here that you have the option to purchase an annual license.
Note: When you click the Add button, your account will be charged the annual license price. There will not be any additional confirmation or “are you sure” screens.
33
33
Launching the Software
When you launch the software, you have two options. You can Copy to Service Catalog or Launch CloudFormation. If you choose the Launch CloudFormation option, you will be then taken to the CloudFormation service in the AWS console. This is the preferred method and will be covered in the next section.
34
34
Service Catalog Option
From the Launch screen, if you chose the Copy to Service Catalog option, you will be able to copy the CloudFormation template to the AWS Service Catalog.
35
35
Copying to the Service Catalog
After you copy the configuration to the AWS Service Catalog you will see a success message and you have the option to view the Service Catalog.
36
36
Launching the Teradata Database from the AWS Marketplace
37
37
Teradata CloudFormation Template
After clicking the Launch button from the AWS Marketplace, you will be logged into the AWS Console and taken to the CloudFormation service and the Teradata Database Enterprise template.
The first screen you will see is the Select Template. From this screen you need to make sure that the region you want to launch into is correctly selected. If not, select the Region you want from the drop down menu. After validating the correct Region, you will need to click the Next button.
38
38
Specify Details – Teradata Database
After clicking the Next button you will be taken to Specify Details screens. In this screen, you will specify the Teradata Database parameters.
You must specify the Stack name, System Name, and DBC Password. For the Japanese Support, NTP Servers and System Timezone parameters, you can elect to take the defaults.
The Stack name is what you will see in the CloudFormation service.
39
39
Teradata Database Parameters
Teradata Database Parameters (cont.)
Continuing down the Teradata Database Parameters screen, you will specify whether you want to enable Temporal, Secure Zones, Row-Level Security and Teradata Intelligent Memory.
If you choose to enable Teradata Intelligent Memory, you will specify a percentage number. By default, it is disabled.
40
40
Node Configuration Parameters
After the Teradata Database Parameters, the next set of parameters will be for the Node Configuration. Here you will specify the Number of Nodes, the Instance and Storage Type, and whether you will want to have the system Unfolded at launch time or if you want the system to have the ability to unfold the system after launch.
If you have the system unfolded or unfold ready, additional private IPv4 addresses will be assigned to the instances when they are created and entries will be made into the host file. If you choose none, you will be able to unfold the system, but must run additional commands to configure the additional private IPv4 addresses prior to unfolding the system.
Data Storage only applies if you choose an m4 instance type. With m4 instances, you will also have the ability to expand your storage after creation. The i2 and d2 instance types have fixed storage sizes and cannot be expanded.
The last two node configuration options have to do with encryption. EBS Encryption are for the data volumes attached to the nodes and Root Disk Encryption is for the local system disk.
41
41
VPC/Network Parameters
Required and must already exist
After the Node Configuration parameters, you will supply the VPC/Network parameters. You will choose which VPC and subnet to launch into, from existing VPCs and Subnets in the drop down menus.
Database Placement Group is a required parameter and you must also have created a Cluster Placement Group prior to launching the template. You will enter the name. If you do not remember the name, you can go to the EC2 Dashboard and select Placement Groups. Note: if you mistype the name, the template will fail after launch.
Elastic IPs are static public IP addresses that will be assigned to each of the DBS nodes. It is recommended for the Teradata Database to choose Yes for the Elastic IPs option.
42
42
Cluster Placement Group
In the CloudFormation template, Placement Group is a required parameter
You must also have created a Cluster Placement Group prior to launching the CloudFormation template. If you did not create a Placement Group, you can go to the EC2 Dashboard, select Placement Groups and then click Create Placement Group.
43
43
Cluster Placement Group (cont.)
A Cluster Placement Group clusters instances in a single Availability Zone to provide low latency and higher network throughput
A spread placement group spreads instances across distinct hardware to improve redundancy
In this screen, you will need to supply a Name and a Strategy. The Strategy is either Cluster or Spread. For Teradata we want Cluster.
A Cluster Placement Group clusters instances in a single Availability Zone to provide low latency and higher network throughput.
A spread placement group spreads instances across distinct hardware to improve redundancy.
44
44
Security Group and Key Pair
Typically this would be your VPN IPv4 address
Back to the template, the last set of parameters are Security Group and Key Pair. For the Remote Access From parameter, you will enter the CIDR block of the IPv4 addresses that will allow access to the Teradata Database instances. Rules will be added for ports 22 (SSH) and 1025 (Teradata Database). This means that only traffic from those IPv4 addresses will be allowed to access the Teradata Database instances. All other traffic will be denied. This is for security purposes. If you do not know which IPv4 addresses you want to allow access to at this time, you can supply the CIDR block of the subnet you are launching the instances into. You will then need to explicitly allow other traffic from outside the Subnet by editing the Security Group after launch.
After entering in all of the parameters, click the Next button.
45
45
Options – Tags and Permissions
The next step is to select Options. The first Options you can specify are Tags. Tags are key/value pairs that AWS assigned to the resources. This can be helpful when you need to track resource utilization and consumption at a more detailed level than just your AWS account. These Tags can be used as filters in monitoring and billing services.
For Permissions, you can choose an IAM Role from the drop down menu or enter a Role ARN (Amazon Resource Name). When you launch the template, it will create various resources such as EC2 instances, and in order to be able to do that, you need have explicit permissions. Roles are a collection of those permissions, and AWS administrators can create roles and assign those roles to selected IAM Users to better control who can create resources, since resources have associated costs.
This is optional and if you do not enter anything here, the permissions will be taken from the user credentials used at login. If the necessary permissions are not assigned, the template will fail with a permission error at the time the resource is created in the template.
46
46
Rollback Triggers
Rollback Triggers allow you to monitor the creation of the resources in the CloudFormation Template, and rollback the creation if the alarms set here are triggered.
47
47
Advanced Options
Further down the Options screen you will have additional options under Advanced. You can choose to send notifications using SNS (Simple Notification Service), set a Timeout value (in minutes) in which the CloudFormation will rollback, and assign a stack policy to define the resources that you want to protect from unintentional updates during a stack update.
Note: If you are trying to troubleshoot, it is recommended to set Rollback on failure to No.
After you set whatever options you want, click Next to go the Review screen.
48
48
Create Stack – Review Parameters
Before creating your stack, you have ability to review your selections. If you want to make any changes, click the Specify Details link or Options link to go back to those sections and make changes.
49
49
Review Parameters (cont.)
Scrolling down, you will review the Node Configuration, VPC/Network, Security Group and Key Pair parameters.
50
50
Review – Options
Scrolling further, you will review the Options you entered.
51
51
Create the Stack
At the bottom of the Review screen you must check the “I acknowledge…” box. After checking the box, you can click Create button to begin the creation process.
52
52
What we just
accomplished…
✓
Launched Teradata
in the cloud
© 2016 Teradata
53
53
Monitoring the Creation of the CloudFormation Stack
54
54
Monitor Stack Creation
After clicking the Create button, you will be taken to the CloudFormation service. In the upper right, click the Refresh button and you should see your Stack. Under Status, you should see CREATE_IN_PROGRESS.
Select the box next to the Stack Name and you will be able to monitor the events in the bottom half of the screen.
55
55
Stack Creation
Do NOT try to SSH into an instance during creation, it may cause the stack to fail
To monitor the stack creation progress:
➢ From AWS CloudFormation console, ensure CREATE_IN_PROGRESSdisplays in the Status column
➢ After the stack is created, ensure CREATE_COMPLETE is displayed in the Status column
➢ If the stack fails, scroll back through the Events to find the failure and reason (highlighted in RED)
➢ After the stack is created, the Teradata Database is ready and started
➢ No need to run tdc-init or tdc-start
During the creation, do NOT try and access any of the resources. You need to wait until the creation completes. You can follow the creation progress by scrolling through the events. If there is a failure, you will need to find the failure message (highlighted in red) for the reason for the failure.
56
56
Monitor Stack Completion
After the Stack successfully completes, you will see CREATE_COMPLETED in the Status column. If you go to the EC2 Dashboard, you will be able to view your instances in a running state.
57
57
What Causes a Stack Failure?
Exceeding your AWS account limits
Resources within the AWS region are not available
VPC CIDR Block specified overlaps with another VPC CIDR Block within your AWS account
Permissions not assigned to the IAM role assumed for your AWS account
If the stack fails, you will need to fix the error and launch the stack again
The template is very stable and the reason for failures are usually outside of the template itself; e.g. permissions, resources, or network setup.
58
58
What Causes a Stack Failure? (cont.)
You must launch into an existing VPC and Subnet
Make sure the following options are enabled:
➢ For the VPC: DNS Hostnames and DNS Resolution should be set to yes
➢ For the Subnet: Auto-assign public IPv4 address must be set to yes
There must be an Internet Gateway attached to the VPC
The VPC Route table needs to have a route to the Internet for the IGW
Since you must launch into an existing VPC and Subnet, you need to make sure the following options and rules are set.
Make sure the DNS Hostname and DNS Resolution for the VPC are set to yes. Make sure the Auto-assign public IPv4 address is set to yes for the subnet.
There must be an Internet Gateway attached to the VPC and the VPC’s route table must have n route to the Internet (0.0.0.0/0) for the IGW.
59
59
EC2 Dashboard
After the stack completes, from the EC2 Dashboard, you will see the database instances are running. If you select one of the instance, you will be able to see the instance details.
60
60
What we just
accomplished…
✓
Spun up Teradata
in the cloud
© 2016 Teradata
61
61
Teradata Database Security Group
62
62
Security Groups and EC2 Instances
Security Groups are used to firewall your instances to control incoming traffic
They operate at the instance level
Support ALLOW rules only
Are stateful (outgoing traffic is allowed)
Maximum 50 rules per Security Group
Security Group
EC2
Instance
EC2
Instance
EC2
Instance
EC2
Instance
In AWS, every instance must have a Security Group assigned. Security Groups are firewalls for your instances to determine what traffic is allowed.
63
63
Editing the Security Group
It may be necessary to edit the Security Group that was created for the Teradata Database instances. From the instance details, you can click on the Security Group link to view the Security Group rules that were created by the template.
64
64
Viewing the Security Group Rules
From the CloudFormation template
In the CloudFormation template, we specified in the Remote Access From parameter, the IPv4 address of our client. So when the Security Group was created in the CloudFormation template, access to the Teradata Database (1025) and Teradata Database instance (SSH 22) will only be allowed from that IPv4 address. All other traffic will not be allowed.
65
65
Editing the Security Group Rules
Before
After
If you want to edit the Security Group rules after the Security Group has been created, you can click the Edit button.
66
66
Connecting to the Teradata Database via Teradata Studio™
67
67
Setting Up Teradata Studio™
To create a new Teradata database connection, click on the new connection profile icon.
68
68
Setting Up Teradata Studio™ (cont.)
From the “New Connection Profile” dialog, choose Teradata and supply a name for the new connection, then click the Next button.
In the “New Teradata Connection Profile” dialog, supply the Public IPv4 address or the Public DNS (IPv4) for one of the database instances, the User Name dbc, and the dbc Password that you supplied in the CloudFormation template.
If you want to test the connection first, click the Test Connection button to make sure the information you entered is able to establish a connection with Teradata.
Finally, click the Finish button to be connected.
69
69
Connected Using Teradata Studio™
After connecting, you will be able to interact with the database. From the Query Development window, you can submit a query.
70
70
Launching Viewpoint from the AWS Marketplace
71
71
AWS Marketplace – Viewpoint
https://aws.amazon.com/marketplace/search/results?searchTerms=“viewpoint”
Searching for “viewpoint” in the AWS Marketplace will display the various Teradata Viewpoint options you can choose.
Clicking Teradata Viewpoint (Single Teradata System) link will take you the product overview page.
72
72
Product Overview
This is the first page that will be displayed after clicking the Teradata Viewpoint link.
73
73
Pricing Information
Scrolling down will then display pricing information. Note that the software charges are $0. Viewpoint is included with the Teradata Database Enterprise software that you subscribed to earlier. But this version will only allow you to monitor one system, so it is more appropriate for a test/dev type of environment, not a production environment where you would need the multi-system version.
74
74
Usage Information
Continuing to scroll, you will see the Usage Information. From this page, you also have links to additional documentation.
75
75
Support Information
Finally, the last page will display the link for both Teradata Support and AWS Support.
76
76
Subscribe
1st
2nd
1. From the product overview page you will click on the Subscribe button. Clicking the subscribe button will take a few minutes to create the subscription.
2. After you have a subscription, you then click on the Configuration button.
77
77
Configure the Software
After clicking the Continue to Configuration button on the previous screen, you will need to make a few configuration choices. There is only one fulfillment option. For software version, you can choose 16.20 or 16.10 and you must choose the region to launch the software. After making you choices, click the Continue to Launch button.
78
78
Launch the Software
On the Launch page, you have a choice to Launch through EC2. This option will take you the EC2 Dashboard menus to launch the Viewpoint AMI. You will need to make the configuration choices using the AWS Console. If you choose Launch from Website, you will make you configuration choices from this web site. The last action is to copy this configuration to the AWS Service Catalog.
Choosing Launch from Website, the EC2 Instance Type is only m4.2xlarge.
79
79
Launch the Software (cont.)
Scrolling down the Launch the Software page, you will next choose the VPC and Subnet to launch the software into.
For Security Group you can choose an existing Security Group or choose to create a new Security Group.
80
80
Creating New Security Group
If you choose to create a new Security Group, you will give the Security Group a name and you can then choose the CIDR blocks in which you will be opening up the ports required by Viewpoint.
Note: port 61616 is need to ActiveMQ and port 5432 is required for PostresSQL.
After you click the Save button, you will then be able to see that the Security Group has been created if you go to the AWS console, EC2 Dashboard and then choose Security Groups menu option.
Note: If you launch into an existing Security Group you will need to make sure that rules for ports 22 (SSH), 80 (HTTP), 61616 (ActiveMQ), 443 (HTTPS) and 5432 (PostgreSQL) exist, or are added.
81
81
Successful Launch
After making your configuration choices, you will see that the software has been successfully deployed.
82
82
EC2 Dashboard – Viewpoint Details
After deploying the software, if you go the EC2 Dashboard, you will now see the Viewpoint instance along with the 2 node Teradata database instances launched previously.
Using the public IPv4 address, you can now connect to Viewpoint through a web browser.
83
83
Connecting and Configuring Viewpoint
84
84
Connecting to Viewpoint
In the address bar of your browser enter the Public IPv4 address
The admin password is the Viewpoint Instance ID
To connect to Viewpoint through a web browser, you will need to enter in the Public IPv4 address. Since this is currently open to all traffic it will not be considered secure and many browsers will display a warning message to that effect.
For AWS, the default admin password is the Viewpoint Instance ID. So you will need to go the EC2 Dashboard and copy and paste the Instance ID into the Password field. You can change the password for the admin user in the Administration portlets – User Manager.
85
85
Configuring Teradata System
After logging into the Viewpoint server, you will need to display the Administration portlets. To view them, in the upper right hand corner, click the Tools icon with the crossed wrench and screw driver.
Clicking Tools will display the various Administration portlets. Choose the Monitored Systems portlet.
86
86
Monitored Systems Portlet
After selecting the Monitored Systems portlet, click the + sign and choose Add Teradata System.
Note: since this is a single system version of Viewpoint, you will only be able to view one of the available systems. If you want to add more than one system, you would need to deploy the multi-system version of Viewpoint.
87
87
Adding Teradata System
After clicking Add Teradata System, you must setup the General parameters.
The first parameter defines a System Nickname for the system you are adding. You will also want to check the Enable system box. The next parameter is the TDPID. For this parameter enter the Private IPv4 address. Again, you can get this from the EC2 Dashboard display for the instance. Do not choose the Public IPv4 address. This instance have been deployed with the VPC on AWS, not externally.
You then will need to supply the Password for tdwm user; the default password is tdwmadmin. After entering in the password, you can then test your connection to the database. If you do not get a successful connection, check that you entered in the correct Private IPv4 address. Another issue is that the Teradata database Security Group is not allowing traffic from the Viewpoint Security Group. We will cover that issue the next slides.
Under Collectors, check the Enable data collectors box. If you do not, you will need to enable the data collectors individually from the Data Collectors setup page that is found underneath General in the Setup menu to the left. Data Collectors are used to collect data that will be stored in the PostgresSQLdatabase on the Viewpoint server and is used to populate the various user portlets. If you do not enable data collectors, your user portlets will be empty when you open them.
‹#›
Lastly, if you have deployed the Enterprise version of Teradata, you must check the box for Enhanced TASM Functions to enable TASM Workload Management functionality.
© 2016 Teradata
88
88
Allow Traffic from Viewpoint
If your connection to the Teradata database fails, if could be because the Teradata database Security Group is not allowing traffic from the Viewpoint Security Group. In the display, you can see that the Viewpoint Security Group (called ViewpointSG) is not displaying as an allowed inbound source.
In this case we must Edit the Security Group to add the Viewpoint Security Group as an inbound source.
89
89
Edit Teradata Security Group
Click the Add Rule button. Then, from the Type drop down menu, choose All traffic and in the Source columns, choose Custom and enter the Viewpoint Security Group ID. You can get this ID from the EC2 Dashboard, Security Groups menu option. After making those entries, click the Save button.
90
90
Traffic Allowed from Viewpoint
You can now see all inbound traffic from the Viewpoint Security Group will be allowed into the Teradata database Security Group.
After making these additions, the Viewpoint server should be able to successfully connect to the Teradata database.
91
91
Viewpoint Dashboard
Closing the administration portlets, you can then click on the Dashboard icon to display the dashboard for the Teradata system.
92
92
Scaling Teradata Database Instances Up or Down
93
93
Scaling Instances Up or Down
You can only change the EC2 instance type to a larger or smaller instance type within the same instance family
Follow these steps to scale the Teradata instances Up or Down:
➢ Shutdown the Teradata Database
➢ Stop the Teradata database EC2 instances
➢ Change the EC2 instance type of each Teradata instance separately
➢ Start the Teradata database EC2 instances
After starting the Teradata EC2 instances, the Teradata database will be running on the new instance types
Scaling up or down is changing the EC2 instance types to a larger or smaller instance type within the same instance family. You cannot change from an m4 instance family to an m5 instance family.
To change the instance family you will do the following:
• Shutdown the Teradata database
• Stop the EC2 instances
• Change the instance type
• Start the EC2 instances
Note: after starting the EC2 instances, the database will be started automatically. This is the default setting.
94
94
Shutdown the Teradata Database
To shutdown the Teradata Database, you must SSH into one of the nodes. When you are logged onto the node, you will see information related to the Teradata database tier and EC2 instance information. In this case we are running the Enterprise tier on a m4.4xlarge instance type.
1. From the command line, you need to enter “sudo su –” to switch to the supervisor.
2. To display the Teradata Database state, enter “pdestate –a” and you will see that the database is running, logons are enabled and the system is currently quiesant.
3. To shutdown the database, you need to enter “tpareset –x shutdown” the –x option says shutdown and the next parameter is a required comment, in this case we just entered shutdown, but it could have been any comment. Note, if you want to restart the database, which is a common task, then enter –f.
4. After entering the tpareset command, you will be prompted to reply, in this case we enter “y”, to shutdown the database.
5. Entering “pdestate –a” again, you see that the database has been shutdown.
95
95
Stopping the EC2 Instances
After the database has been shutdown, from the EC2 Dashboard, select each of the Teradata database nodes and from the Actions drop down, select Instance State and Stop.
When prompted to stop the instances, click the Yes, Stop button.
96
96
Change the Instance Type
To change the instance type, you must do it individually. So select one Teradata database instance and from the Actions drop down, select Instance Settings and Change Instance Type.
97
97
Change the Instance Type
Even though you will see all of the different instance types, you can only change to another supported instance type in the family
If you choose an unsupported instance type you will get an error that it is not supported
In this case, we chose to change from an m4.4xlarge to m4.10xlarge.
Note: Even though you will see all of the different instance types, you can only change to another supported instance type in the same instance family. If you choose an unsupported instance type you will get a prompt that it is not supported.
98
98
Change the Instance Type
You can now see that the instance type is now m4.10xlarge. The next step is to start the Teradata database.
99
99
Starting the Teradata Database
Select the Teradata database instances and from the Actions drop down, select Instance State and Start.
You will be prompted to start the instances, click the Yes, Start button.
100
100
Starting the Teradata Database
After starting the instances, which can take about 3-5 minutes, you will see that the Teradata database is now running on m4.10xlarge instances.
101
101
Validate Teradata has Started
After the instances are started, the default setting is to also start the Teradata database. You do not need to enter any additional start commands to bring the database up.
You can now see that the database is now running on the new instance types, in this case m4.10xlarge. And when you enter “pdestate –a”, the database is running.
102
102
Scaling Teradata Database Instances In and Out
103
103
Scaling Instances In or Out
Scaling instances in or out is also known as folding or unfolding
Unfolding adds more Compute, Memory, I/O Bandwidth and Parsing Engines (PEs) to the configuration
Follow these steps to scale the Teradata instances In or Out:
➢ Shutdown the Teradata Database
➢ Enter the commands to start the folding or unfolding process
After folding or unfolding process completes, the Teradata Database will be running on the new configuration
The number of AMPs and disk storage remains the same
Scaling is also know as unfolding or folding. You can unfold or fold with a factor of 2x or 4x. Unfolding adds additional, CPU, memory, I/O bandwidth and PEs. It does not add more AMPs or storage.
To unfold a system, you need to shutdown the database and enter the commands to start the unfolding or folding process. After the process completes, the database will be running on the new configuration.
104
104
What Happens During an Unfold?
If you want to unfold a 2 node system 2x, to a 4 node system, the following steps will be performed during the unfold process:
➢ 2 more nodes will be provisioned within the same cluster placement group
➢ Half the EBS storage disks will be detached from the existing nodes
➢ The detached EBS storage disks will be attached to the new nodes
➢ The new nodes will be clustered with the existing nodes
You can unfold a system 2x or 4x. So for example, you want to unfold a 2 node system 2x to a 4 node system, the following steps will be performed during the unfold process:
• 2 new nodes will be provisioned within the same cluster placement group
• Half of the EBS storage disks will be detached from the existing nodes
• Attached the EBS storage disks to the new provisioned nodes
• Cluster the nodes for fallback protection
105
105
What Happens During an Unfold?
Before
2 Nodes
After
4 Nodes
This example shows a 2 node system being unfolded to a 4 node system.
106
106
Displaying the Current Configuration
The tdc-unfold –d command will display the current configuration and what unfold options you have. We can unfold this system using either the 2x or 4x options.
107
107
Before Starting the Unfold Process
Before starting the unfold process, we have 2 nodes
Before starting the unfolding, you can see from the EC2 Dashboard, there are 2 database instances.
108
108
Shutdown the Teradata Database
Before starting the unfold process, we have to shutdown the database
Before starting the unfold process, we need to shutdown the Teradata database.
To shutdown the database: 1. From the command line, you need to enter “sudo su –” to switch to the
supervisor.2. To shutdown the database, you need to enter “tpareset –x shutdown” the
–x option says shutdown and the next parameter is a required comment, in this case we just entered shutdown, but it could have been any comment. Note, if you want to restart the database, which is a common task, then enter –f.
3. After entering the tpareset command, you will be prompted to reply, in this case we enter “y”, to shutdown the database.
4. Entering “pdestate –a” again, you see that the database has been shutdown.
109
109
Starting the Unfold Process
In this example we issued the command to unfold the system 2x. The current configuration is displayed along with what the configuration will be after it is unfolded.
Note: From the notes, the unfolded system will consume additional resources and add additional costs. It will increase performance but it will not give you additional storage capacity. If you want additional storage capacity you can do that using the tdc-expand-storage command.
Entering “yes” to the continue command, starts the unfolding process.
110
110
Completing the Unfold Process
After entering “yes” to start the unfold process, you can see that in this case, unfolding a system from 2 nodes to 4 nodes, took approximately 10 minutes. The estimated time for an unfold 2x is 20 minutes.
After the unfold process completes successfully, the current configuration is now 4 nodes from 2 nodes. The number of PEs went from 4 to 8 total, the number of AMPs remained at 40 total, but the number of AMPs per node went from 20 to 10. Also, the total CPUs went from 32 to 64 and the total memory went from 130GB to 260GB.
Also note: that after the unfold process is completed, the database is up and running.
111
111
After the Unfold Process Completes
After the unfold process completes, we have 4 nodes
After the unfolding, you can see from the EC2 Dashboard, there are 4 database instances.
112
112
Expanding EBS Storage
113
113
Expanding EBS Storage
Allows the customer to start small and grow when needed, avoiding
paying for higher non-utilized storage
EBS Storage can be expanded after Database instances are
launched without reconfiguring the system
Customers can now select any storage value from 5TB to 60TB, per
node, and have the ability to expand their storage in 1TB increments
Expanding storage increases the size of each pdisk EBS volume on
the system up to a maximum of 3TB
Expanding storage allows customers to expand existing EBS storage volumes.
Total EBS storage per node can be specified from a minimum of 5TB to 60TB, and you have the ability to expand the storage in 1TB increments up to the 60TB total.
The maximum EBS storage per disk is 3TB.
114
114
Expanding EBS Storage (cont.)
Does not increase the number of AMPs per node
Requirements to expand storage:
• System can not be in an unfolded state
• Must have 20 AMPs/EBS volumes per node before expansion
• Can only be done for m4 instance types
To be able to expand EBS storage, the system must be in an unfolded state and is only available on the m4 instances which support EBS storage. The i2 and d2 instances support local storage, not EBS storage.
115
115
Shutdown the Teradata Database
Before starting the storage expansion, we have to shutdown the database
Before starting the storage expansion, we need to shutdown the Teradata database.
To shutdown the database: 1. From the command line, you need to enter “sudo su –” to switch to
supervisor privileges.2. To shutdown the database, you need to enter “tpareset –x shutdown” the
–x option says shutdown and the next parameter is a required comment, in this case we just entered shutdown, but it could have been any comment. Note, if you want to restart the database, which is a common task, then enter –f.
3. After entering the tpareset command, you will be prompted to reply, in this case we enter “y”, to shutdown the database.
4. Entering “pdestate –a” again, you see that the database has been shutdown.
116
116
Starting the Storage Expansion
In this example, we are going to increase the total storage by 5TB. This will increase each EBS volume 125GB.
Respond “yes” to the prompt to start the expansion process.
117
117
Completing the Storage Expansion
At the completion of the storage expansion, the database will be started with the additional storage available.
118
118
Scaling Query Comparison
119
119
AWS Sample Query Comparisons
Scale Out
Sample query aggregates sales data from the Sales Transaction Line table and joins it to the Item and Brand tables to report quarterly sales by Brand
# Nodes
(m4.4xlarge)
Database
Physical Design
Elapsed
Time
2 (40 AMPs) PI only 1:04
2 (40 AMPs) Row Partitioning 0:03
4 (40 AMPs)
Unfolded
PI only 0:32
4 (40 AMPs)
Unfolded
Row Partitioning 0:01
The table above compares a sample query which does an aggregation from a large sales transition line table and reports it by brand and item. The top rows compare the elapsed times on a 2 node m4.4xlarge reading data from a sales transaction line table with only a primary index and from a sales transaction line table with row partitioning implemented. The bottom rows compare the same query after unfolding the 2 node system to a 4 node system. Unfolding the system added more CPU, memory, and I/O bandwidth. The numbers of AMPs and storage space remained the same. By adding more hardware, we can see about a 50% improvement in performance over row partitioning alone.
© 2016 Teradata
120
120
AWS Sample Query Comparisons
Scale Up
Sample query aggregates sales data from the Sales Transaction Line table and joins it to the Item and Brand tables to report quarterly sales by Brand
Instance Size
(2 nodes)
Database
Physical Design
Elapsed
Time
Instance
CPUs
Instance
Cost
m4.4xlarge PI only 1:04 16 $0.80
m4.4xlarge Row Partitioning 0:03
m4.10xlarge PI only 0:29 40 $2.00
m4.10xlarge Row Partitioning 0:01.7
m4.16xlarge PI only 0:12.5 64 $3.20
m4.16xlarge Row Partitioning 0:00.9
In this test, we compared the performance of the same query on the 2 node m4.4xlarge against a 2 node m4.10xlarge and 2 node m4.16xlarge. By scaling up, we are adding faster CPUs and more memory. The m4.10xlarge comparably, has 2.5 times more CPUs than the m4.4xlarge and the m4.16xlarge has 4 times more CPUs along with more memory.
© 2016 Teradata
121
121
Partitioning Explanation
Why does the query perform better with row partitioning?
Sales Transaction Detail table table defined without Row Partitioning across 4 AMPs
Rows are ordered by Row Hash
SELECT … WHERE TxnDate = DATE '2018-01-03’;
Full Table Scan is executed
'01' 1028 2018/01/03
'12' 1031 2018/01/03
'28' 1032 2018/01/03
'03' 1016 2018/01/02
'17' 1013 2018/01/02
'48' 1023 2018/01/02
'14' 1001 2018/01/01
'35' 1007 2018/01/01
'39' 1011 2018/01/01
'23' 1040 2018/01/04
'30' 1038 2018/01/04
'42' 1047 2018/01/04
RH Txn# TxnDate
'10' 1034 2018/01/03
'29' 1033 2018/01/03
'34' 1029 2018/01/03
'07' 1017 2018/01/02
'16' 1021 2018/01/02
'45' 1015 2018/01/02
'06' 1009 2018/01/01
'26' 1002 2018/01/01
'36' 1012 2018/01/01
'13' 1037 2018/01/04
'21' 1045 2018/01/04
'36' 1043 2018/01/04
RH Txn# TxnDate
'19' 1025 2018/01/03
'40' 1035 2018/01/03
'47' 1027 2018/01/03
'09' 1018 2018/01/02
'27' 1014 2018/01/02
'44' 1022 2018/01/02
'04' 1008 2018/01/01
'24' 1004 2018/01/01
'32' 1003 2018/01/01
'05' 1048 2018/01/04
'15' 1042 2018/01/04
'33' 1039 2018/01/04
RH Txn# TxnDate
'25' 1036 2018/01/03
'31' 1026 2018/01/03
'46' 1030 2018/01/03
'02' 1024 2018/01/02
'11' 1019 2018/01/02
'22' 1020 2018/01/02
'08' 1006 2018/01/01
'20' 1005 2018/01/01
'43' 1010 2018/01/01
'18' 1041 2018/01/04
'38' 1046 2018/01/04
'41' 1044 2018/01/04
RH Txn# TxnDate
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
✓
So why does the query perform dramatically better when we implemented row partitioning. In the table without row partitioning, the rows are uniformly distributed across the available AMPs based on the Row Hash of the primary index column vale and then each AMP will order the rows by the Row Hash of the primary index value. In this case, when we need to extract rows for a particular date, all of the rows on each AMP will need to be read.
© 2016 Teradata
122
122
Partitioning Explanation (cont.)
Why does the query perform better with row partitioning?
Sales Transaction Detail table table defined with Row Partitioning across 4 AMPs
Rows are ordered by Partition (TxnDate) and Row Hash
SELECT … WHERE TxnDate = DATE '2018-01-03’;
Single Partition Scan is executed
'14’ 1001 2018/01/01
'39’ 1011 2018/01/01
'01’ 1028 2018/01/03
'35’ 1007 2018/01/01
'17' 1013 2018/01/02
'42’ 1047 2018/01/04
'03’ 1016 2018/01/02
'28’ 1032 2018/01/03
'23’ 1040 2018/01/04
'48’ 1023 2018/01/02
'12' 1031 2018/01/03
'30’ 1038 2018/01/04
RH Txn# TxnDate
'36’ 1012 2018/01/01
'29' 1033 2018/01/03
'34' 1029 2018/01/03
'26’ 1002 2018/01/01
'16' 1021 2018/01/02
'36’ 1043 2018/01/04
'06' 1009 2018/01/01
'10’ 1034 2018/01/03
'13’ 1037 2018/01/04
'07’ 1017 2018/01/02
'45’ 1015 2018/01/02
'21' 1045 2018/01/04
RH Txn# TxnDate
'27’ 1014 2018/01/02
'05’ 1048 2018/01/04
'33’ 1039 2018/01/04
'32’ 1003 2018/01/01
'19’ 1025 2018/01/03
'15’ 1042 2018/01/04
'04' 1008 2018/01/01
'44’ 1022 2018/01/02
'40’ 1035 2018/01/03
'24’ 1004 2018/01/01
'09’ 1018 2018/01/02
'47’ 1037 2018/01/03
RH Txn# TxnDate
'25' 1036 2018/01/03
'31' 1026 2018/01/03
'41’ 1044 2018/01/04
'08’ 1006 2018/01/01
'43' 1010 2018/01/01
'22' 1020 2018/01/02
'20' 1005 2018/01/01
'11’ 1019 2018/01/02
'38’ 1036 2018/01/04
'02’ 1024 2018/01/02
'46’ 1030 2018/01/03
'18' 1041 2018/01/04
RH Txn# TxnDate
✓
✓
✓ ✓
✓
✓
✓
✓
✓
✓
✓
✓
When the rows are partitioned by date, the rows are still uniformly distributed by the primary index value Row Hash, but now the rows are first ordered by the partitioned column, date, and then within the partition by Row Hash. This will group the rows for the same date into the same partition. Now instead of reading all of the rows, we only need to read the rows for a single partition, greatly reducing the number of I/O’s and resulting in dramatic performance improvement. This is one of many physical design options available with the Teradata Database that can came result in performance improvement without having to add additional costly hardware. In the case of partitioning, the cost is minimal (2 additional bytes per row for the partition number).
© 2016 Teradata
123
123
Implementing Partitioning
To Implement Partitioning simply add a PARTITION BY clause specifying the partitioning interval
CREATE SET TABLE SALES_TRANSACTION_LINE_PPI ,
( Sales_Tran_Id INTEGER TITLE 'Sales Tran Id' NOT NULL,
Sales_Tran_Line_Num SMALLINT TITLE 'Sales Tran Line Num' NOT NULL,
Item_Id DECIMAL(15,0) TITLE 'Item Id' NOT NULL,
Item_Qty SMALLINT TITLE 'Item Qty' NOT NULL,
Unit_Selling_Price_Amt DECIMAL(8,4) TITLE 'Unit Selling Price Amt' NOT NULL,
Unit_Cost_Amt DECIMAL(8,4) TITLE 'Unit Cost Amt',
Tran_Line_Status_Cd CHAR(1) TITLE 'Tran Line Status Cd',
Sales_Tran_Line_Start_Dttm TIMESTAMP(6) TITLE 'Sales Tran Line Start Dttm',
Tran_Line_Sales_Type_Cd CHAR(2) TITLE 'Tran Line Sales Type Cd',
Sales_Tran_Line_End_Dttm TIMESTAMP(6) TITLE 'Sales Tran Line End Dttm',
Tran_Line_Date DATE FORMAT 'yyyy-mm-dd',
location_id INTEGER )
PRIMARY INDEX ( Sales_Tran_Id )
PARTITION BY RANGE_N(Tran_Line_Date BETWEEN DATE ‘2015-01-01' AND DATE ‘2019-12-31'
EACH INTERVAL '1' DAY );
To implement partitioning, you simply need add a PARTITION BY clause. In this example, we are using the keyword RANGE_N to partition the data by an ascending range of values. In this case, by the partitioning column Tran_Line_Date. We are going to create daily partitions between the dates of 2015-01-01 and 2019-12-31.
© 2016 Teradata
124
124
Summary
125
125
DIY Deployment on AWS Summary
In this presentation, we covered:
➢ The Teradata Database software in the AWS Marketplace
➢ How to Launch the Teradata Database from the AWS Marketplace
➢ How to monitor the creation of the CloudFormation stack
➢ The Teradata Database Security Group that is created
➢ How to connect to the Teradata Database via Teradata Studio™
➢ How to launch Viewpoint from the AWS Marketplace
➢ How to connect to and configure Viewpoint
➢ How to scale the Teradata Database instances up or down
➢ How to scale the Teradata Database instances in and out
➢ How to expand EBS Storage
126
126
Cloud Consumption Options
© 2016 Teradata
127
127
Cloud Consumption Option #1
Do-it-yourself Deployment
“I’ll deploy & manage in AWS myself.”
• Benefit: Broad system customization
• Use cases recommended:
• Proofs of Concept
• Test & Development
• Discovery Analytics / Data Labs
© 2016 Teradata
128
128
Cloud Consumption Option #2
IntelliCloud as-a-service
“Deploy in AWS & manage it for me.”
• Benefit: No babysitting required!
• Use cases recommended:
• Production Analytics
• Disaster Recovery
• Test / Dev / QA / Data Labs
© 2016 Teradata
129
129
IntelliCloud for AWS Attributes
• Predictable cost• Flexible pricing, no hidden fees
• Convenient subscription options• Start small and grow as needed
• “Just bring your data and a DBA”• We manage the environment for you
Service Feature Included
Software ✓
Infrastructure ✓
Monitoring ✓
Encryption ✓
Compliance ✓
Web Console ✓
Onboarding ✓
Up to 99% SLA ✓
Backups ✓
© 2016 Teradata
130
130
IntelliCloud Compliance Audits
• Audited for compliance• GDPR
• PCI
• HIPAA
• SOC 1 and 2
• ISO 27001
• Designed to comply• EU Model Clauses
• EU-US Privacy Shield
• Additional regulations
We invest ~$1M each year in recurring third-party audits
© 2016 Teradata
131
131
Elasticity and Cost Optimization
•View site details
•View utilization
• Scale compute
• Stop/Start database
•Modify backup schedule
• Set firewall rules (coming)
© 2016 Teradata
132
132
IntelliCloud Management Console
© 2016 Teradata
133
133
System Resources
This is the IntelliCloud Management Console (IMC) dashboard. The top pane displays the various systems managed by IntelliCloud and the bottom pane displays the details about those systems.
In the Dashboard, you can view specific details for a database site by selecting it in the Database Sites pane and scrolling down the page.
The Database Sites pane includes CPU and disk space utilization based on the average of all nodes for the last 24 hours.
In this example, the AWS system in us-west-2 region, is at 21% disk utilization and 73% CPU utilization over the last 24 hours.
This system is a development system running Teradata Database version 15.10. It is deployed on 16 m4.10xlarge instances with 20TB per node, 320TB total. The current AWS configuration is 20 AMPs per node, so each AMP is managing 1TB of data.
134
134
Resource Utilization
Scrolling down you will see the Utilization report. Utilization displays a graph of the CPU load and amount of storage used over time. You can configure the this report to display by day, week or month intervals.
135
135
Separate Compute and Storage
Moving your cursor along the high or low peaks will display a popup showing the CPU and Disk metrics.
136
136
Backups, IPs, Support Tickets
Continuing to scroll down the Dashboard, the last 3 displays are Backups, Network Settings and Support Tickets.
By default, IntelliCloud sites are backed up daily. The two most recent full backups are retained at the primary data center. Additional backup features depend on the deployment platform.
For Backup Jobs, you edit the backup job by clicking the Edit Backup Job link. This will open a dialog box allowing you to change the backup job schedule.
• Additional backup services are available by submitting a support ticket: Enable auto-restart to re-run a failed backup job.
• Enable weekly or monthly backups.• Suspend execution of backup jobs.• Request NOSYNC option for backup jobs.
For support tickets you can see previously submitted tickets and you can also open a new ticket if you want. The IntelliCloud Management Console provides a convenient interface to the IntelliCloud support portal. Creating a ticket from the IntelliCloud Management Console generates an IntelliCloud support ticket.
137
137
Additional Capabilities
In the upper left corner, if you click the menu icon, you will be displayed with other menu choices. The following slides will show the examples of User Management, Metering and Availability Reports.
138
138
User Management
© 2016 Teradata
139
139
Instance-Specific Metering
The first display in Metering allows you to look at the instance hours consumed on the various instance types over time. You can filter the display by Platform (AWS), Databases and the interval (hourly, daily or monthly) across a specified data range.
140
140
Availability Reports
Availability reports show availability and outage statistics for each IntelliCloud site, including database downtime and network connectivity disruptions.
• Metrics are available on a calendar month basis, for the last 12 months.• Date ranges are in UTC.• Reports are available by the 10th of each month for the previous month.• Click an availability percentage to view the detailed Availability Report
for the target interval, including a list of incidents. • In an Availability Report, click an incident ID to view all details in the
Cloud Service Portal.
Outage exceptions excluded from Availability Reports: Customer's misuse of Cloud Services
• Customer's internet connectivity failure• Non-Teradata internet traffic issues• Scheduled downtime
141
141
Scale Up/Down
© 2016 Teradata
142
142
Current Size = Medium
With IntelliCloud you can scale the system within the same instance family. This is referred to as scaling up or down. From the IMC dashboard, you click on the “SCALE UP/DOWN” link.
143
143
Scale Up from Medium to Large
After clicking on the “SCALE UP/DOWN” link, you will get a popup screen with the other instance sizes within the same instance family that you can choose from. In this example, we are choosing to scale up from a m4.10xlarge instance to a larger m4.16xlarge.
Note: that you there will be additional AWS CPU charges and also the rate of TCore consumption will be higher.
144
144
Just a Restart, No Redistribution
After about 5 to 10 minutes, the scale up will be completed and you will see that the system is now running on m4.16xlarge instances instead of m4.10xlarge instances.
145
145
Scale Out/In
© 2016 Teradata
146
146
Current Config = 16 Instances
With IntelliCloud you can scale the system out or in to increase or decrease the number of nodes. This is referred to as scaling out or in. This will allow you to increase the CPU, memory and I/O bandwidth capacity. It will also increase the number of Parsing Engines (each node will have 2 PEs ), but will not increase the number of AMPs or storage.
From the IMC Dashboard, click the SCALE OUT/IN link.
147
147
Scale Out Compute By 2X or 4X
After clicking the SCALE OUT/IN link, you will get a pop-up screen that will allow you to choose the scaling options you want. 1x, 2x or 4x. In this example, we are going to scale out 2x, from 16 nodes to 32 nodes.
Note that there will be additional AWS CPU charges and also the rate of TCore consumption will be higher.
148
148
Just a Restart, No Redistribution
After about 20 minutes, the scale out will be completed and you will see that the system is now running on 32 m4.16xlarge instances instead of 16 m4.16xlarge instances.
149
149
Stop/Start
© 2016 Teradata
150
150
Optimize Spend When Not Using
With IntelliCloud you can scale the system out or in to increase or decrease the number of nodes. This is referred to as scaling out or in. This will allow you to increase the CPU, memory and I/O bandwidth capacity. It will also increase the number of Parsing Engines (each node will have 2 PEs ), but will not increase the number of AMPs or storage.
From the IMC Dashboard, click the SCALE OUT/IN link.
151
151
Turn Off Compute (Keep Storage)
© 2016 Teradata
152
152
IntelliCloud Management Console
• Provision sites
• View system config, status info
• View compute, storage utilization
• Manage elasticity
• Monitor, manage backups
• Open, monitor support tickets
• Manage user accounts
153
153
What we just
accomplished…
✓
Learned about
As-a-service options
© 2016 Teradata
154
154
Connecting with TableauCloud Analytics Experience
Kevin Bogusch, Cloud Marketing, Teradata
© 2016 Teradata
155
Agenda
155
• Connect with Teradata Studio
• Load our data set
• Connect with Tableau
• Investigate our data set
Follow Me
© 2016 Teradata
156
156
Let’s Load Our Data
© 2016 Teradata
157
157
Start Teradata Studio
• Double-click the Teradata Studio
icon on your remote desktop
• Studio will take about a minute to
get ready
• Studio is available free
for Teradata customers from
https://downloads.teradata.com
© 2016 Teradata
158
158
Create a Connection
• The New Connection Profile
window will appear. If not, on the top right, click Query
Development, then on the left, right-click
Database Connections and select New.
• Click Teradata in the list
• Give it a name, like “CAE”
• Click Next
© 2016 Teradata
159
159
Finishing the Connection
• Enter the IP address of your
database for the server name
• Enter DBC for the user name
• Enter the DBC password that you
used in your stack
• Click Save Password
• Click the Add… button
© 2016 Teradata
160
160
Finishing the Connection
• Select “TCP” from the JDBC Property drop-down
• The TCP Properties window appears
• Select “KEEPALIVE” from the drop-
down
• Click on OK, and then OK again
© 2016 Teradata
161
161
Finishing the Connection
• Click the Finish button
• You will see the connection expand
on the left side
• Click the > (arrow) to expand it to
ensure that you are connected
© 2016 Teradata
162
162
Create a Database
• In the upper right, Click Query
Development
• From the File menu,
choose Open File…
• Select
CAE_attendee_data_demo.sqlfrom the desktop
© 2016 Teradata
163
163
Create a Database
• Click anywhere inside the SQL, just
to make sure the cursor is there
• Press Ctrl+A to select all of the SQL
• Press Ctrl+C to copy it
• Click on the SQL Editor tab
• Press Ctrl+V to paste it
© 2016 Teradata
164
164
Create a Database
• Click the green arrow at the upper
right
• You will know that it is successful if
there are no errors (no red marks) in the bottom window.
© 2016 Teradata
165
165
Load the Data
• Click Data Transfer in the upper
right
• Expand the database connection
on the left:
DBC
→ Databases
→ CAE
→ Tables
→ PARKING_VIOLATION
© 2016 Teradata
166
166
Load the Data
• Right-click on (1)
PARKING_VIOLATION
• (2) Select Data
• (3) Then select Load Data
• Change the source type to
External File
• Click the Launch button
1
2
3
© 2016 Teradata
167
167
Load the Data
• If needed, drag the right edge of
the window a little bit to the right
• (1) Change the file type to
Excel (.xlsx), if needed
• (2) Click the Browse button and
find CAE_parking_violation.xlsx
• (3) Click Column Labels in First Row
• Click the Finish button
• Data will load in about 30 seconds
• You will see Rows Transferred
1
2
3
© 2016 Teradata
168
168
Let’s Visualize Our Data
© 2016 Teradata
169
169
Start Tableau
• Click the Tableau Desktop icon on
your remote desktop
• Tableau should start in less than a
minute
• Thank you to Tableau as a
corporate sponsor!
© 2016 Teradata
170
170
Connect with Tableau
• Click the Teradata Studio icon on
your remote desktop
• On the left, under To a Server,
select More…
• Click on Teradata
© 2016 Teradata
171
171
Connect with Tableau
• Enter the IP address of your
database for the server
• Enter DBC for the user name
• Enter the DBC password that you
used in your stack
• Click the Sign In button
© 2016 Teradata
172
172
Choose Your Database & Table
• In the left-hand menu, click the
down arrow for database
• Enter CAE
• Click the blue plus sign
• Enter parking_violation
• Click the blue plus sign
© 2016 Teradata
173
173
Validate Your Table
• The table appears in the right, near the top
• Click the Update Now button to see
the data
• The data appears below in a
spreadsheet
© 2016 Teradata
174
174
View Your Data
• At the bottom left, click on Sheet 1
• Scroll down the Dimensions box to
the bottom
• Click and drag Violation time up to
the Columns area
• At the bottom left, in the Measures
box, click and drag Number of
Records to the Rows area
© 2016 Teradata
175
175
View Your Data
• In Dimensions, click and drag
Vehicle color on to the “Color” boxin Marks
• To the far right, click Show Me to hide the menu
• In the Vehicle color list, click on the
down arrow (it will appear)
• Click on Sort…
© 2016 Teradata
176
176
View Your Data
• Click the Descending option
• Click on the Field option, and leave
it at “Number of Records”
• Click the OK button
© 2016 Teradata
177
177
View Your Data
• You now have a breakdown of the
number of tickets written at each
hour for the 2018 fiscal year (June
to July), categorized by color
• You can drag Vehicle color off of
the Marks panel and put a different
category there
© 2016 Teradata
178
178
Questions You Can Answer
• Do boroughs differ significantly
when they write their tickets?
• Which agencies write the most
tickets
• What states (based on car
registration) are ticketed the most?
• Does it make a difference what
color your car is?
• What code violation is given the
most and when?
• Are certain vehicle makes targeted
more than others?
© 2016 Teradata
179
179
What we just
accomplished…
✓
Created an
analytic visualization
© 2016 Teradata
180
180
Closing Remarks
© 2016 Teradata
181
181
What Did We Do Today?
• Today you learned:
• How to spin up Teradata in the cloud
• Options for Do-it-yourself and As-a-service
• How to use Teradata Studio for (new) analytics
© 2016 Teradata
182
182
Cloud Consumption Categories
Do-it-yourself“I’ll deploy & manage myself.”
•Benefit: System customization
•Use cases recommended:
• Proofs of Concept
• Test & Development
• Discovery Analytics / Labs
As-a-service“Deploy & manage it for me.”
•Benefit: No babysitting required!
•Use cases recommended:
• Production Analytics
• Disaster Recovery
• Test / Dev / QA / Data Labs
© 2016 Teradata
183
183
Consistency and Portability
Pricing Freedom
Teradata Hardware
Commodity Hardware
Public CloudBYOL
Teradata Cloud
Subscription-based Teradata licenses are portable
© 2016 Teradata
184
184
Strong Services Organization
`ADVISE & ARCHITECT
Advise on Business Outcomes
Helps customers set an analytic vision that aligns business and IT, assesses current state capabilities, and evaluates technology & approaches
DESIGN & IMPLEMENT
Enable an Ecosystem Architecture
Design and implement analytic ecosystems, the underlying data, and platforms
OPTIMIZE & MANAGE
Ensure Value Delivery
Support customers’ analytic ecosystems and drive continuous improvement; includes Support & Managed Services
Artificial Intelligence
Strategy
Business & Analytics
Capability Review
Business & Analytics
Roadmap
Business & Analytics
Governance
Ecosystem Architecture
Definition
Rapid Analytic Consulting
Engagement (RACE)
AnalyticOps &
Optimization
Business Continuity Operations
Managed Database & Application Operations
Managed Ecosystem
Administration
Elastic Provisioning
Ecosystem Upgrades & Migrations
Support Services
Advanced Analytics &
Data Science
AnalyticOps Foundation
BI & Data Visualization
Data, Acquisition & Integration
Data LakeData Platform & Foundation
Data Security & Privacy
Teradata Applications
Data Design & Access
© 2016 Teradata
185
185
Let’s Keep Learning…
• Connect with cloudy colleagues
• Expand your network
• View and read the info on our website
• Many videos, whitepapers, blogs
• Tap into Teradata Education Network resources
• Dozens of online courses
© 2016 Teradata
187
187
Spin Up on Your Own
© 2016 Teradata
188
188
Thank You to Our Sponsors!
© 2016 Teradata
189
189
Take the Survey!
Your input helps us
improve how we serve you
© 2016 Teradata
