When you say "alias" do you mean the text value of the label? You are storing user customizable label text right?
Here's the thing about user controls: When you have an instance of a user control on your page, it becomes just one of many control instances in the page's control tree. The fact that the control starts life as an ascx page is basically irrelevant. So using the ascx file name will be difficult if not impossible (I don't think there is any way to extract that from any class member of the control class).
You would be much better off to use the control's class name. Even better still would be to tag your user control with a custom attribute instead of relying on its class name.
Despite these ideas, I'm concerned with the solution you propose. Putting page and control Ids into the database introduces very tight coupling between your database layer and your presentation layer. This is typically something you should strive to keep well partitioned. What happens if you change a page's controls? Or the page/control file name? What about if you want to reuse various label values in other places but the page/control names don't apply?
For these reasons you should consider establishing keys (possibly text based) to represent the units of text in the database you will use for the label controls text property. The controls/pages that contain these labels can set the label text in their page_load method.
One trick I have used is to utilize the flexibility of the control attributes collection. You could add an attribute to a control's markup tag to identify the key that holds the text you want to assign to it. In the code behind you can interrogate the control's Attributes collection for that value, use it as needed, then remove it.
Although I haven't tried it so I'm not sure if/how it can be done, you might want to look into a custom resource manager. I believe that you can assign some kind of resource binding to controls such that the resource manager handles getting a resource (i.e. a localized string value) and assigning it to the bound property (i.e. <label>.Text). I'd be surprised if you could not create your own resource manager that does just what you need to do (get a user set value from your DB and return that value) but still relies on the standard resource binding for handling the control assignment task. Just in this case you have a custom resource manager to handle user-preferred instead of culture-preferred values.
-Peter
peterlanoie.blog