If you create the Service Application it creates virtual directories under the SharePoint Web Services in IIS. each Service application virtual directory is created by GUID (globally unique identifier).
NOTE An important point to remember is that a service application may have one or more databases. For example, the User Profile service application has profile, synchronization, and social tagging databases. Another example is the Search service application with crawl, link, analytics, and administration databases. The number of databases can quickly add up and be difficult to manage if you do not properly plan capacity.
One issue with confi guring service applications using the Confi guration Wizard is that the associated virtual directory databases can end up having a lot of GUIDs. For example, the name for one of the User Profi le databases could be User Profile Service Application_ProfileDB
Though this might be acceptable in some cases, generally, a more intuitive naming convention makes a more sense. One way to resolve this issue is to use the Manage Service Applications page in the Central Administration site to add service applications individually and then specify meaningful database names. The other alternative approach is to use Windows PowerShell to provision your service applications.
The following code snippet shows how you can provide a State Service service application using Windows PowerShell. Note how the SQL Server database and server name are specifi ed in the code.
New-SPStateServiceDatabase -Name “StateServiceDatabase” -DatabaseServer
“dhsqlsrv” | New-SPStateServiceApplication -Name “State Service Application”
| New-SPStateServiceApplicationProxy -Name ” State Service Application Proxy”
-DefaultProxyGroup > $null
Happy SharePointing …..!!! 🙂 🙂 🙂