I have an account on CPANEL and I want to create a database on mysql but it doesn't appear on the list
You can see in the picture
Your MySQL feature has been disabled by your hosting provider. Please contact them to enable this for your account.
Related
Using Azure Resource Manager.
I have an Azure SQL Database resource, and even when I delete all "allow" firewall (on the sql server's blade) rules, my VM is still able to query the SQL DB.
EVEN when I set "Allow Access" to no for the ip address of the VM, I can still query the DB. How??
Is this because Azure automatically allows resources in the same Resource Group to access it? Even without explicit Firewall allow rules?
Under the Firewall section of the SQL Server blade, there's a switch called "Allow access to Azure services". Having this on will allow any Azure resource to access get through the firewall (they will still need your username and password of course to actually access the server). This includes Azure resources on other people's subscriptions. See this answer.
I had this turned on and that's why my firewall settings made no difference for my VM's.
Not exactly sure what's happening with your specific situation, security-wise, but Resource Groups have nothing to do with it. Resource Groups help organize resources within a single container, where you can manage those resources better (e.g. add users to the Resource Group without adding them to the rest of your subscription). They don't play a role in communication between Azure services.
We have plesk hosting account now we want to migrate to cpanel,approx 5gb mail data in plesk account how to direct transfer Email data from plesk to cpanel.
You can migrate whole account through cPanel migration tool
OR
You can submit migration requesto to cPanel support team. They will help you on this. Here are the some useful information about this.
https://documentation.cpanel.net/display/CKB/cPanel+Migration+Services+and+Guides
I am using OpenERP, i have over 5-6 domains and I would like to have a specific database associated with each domain. Can anyone know how to do multi-tenancy setup on OpenERP?
As I understand it, OpenERP has three application tiers: the database, the application server, and the web server.
If I want to create a working configuration for multiple, independent companies how do i do that ?
You can run each as a separate database on the same server and point all the domains to the same server.
To make sure that they only see their own database, you can add an option to the server startup:
openerp-server --db-filter='%h'
then it will search for a database with the same name as the domain
I'm so sorry if this question is very basic but I'm very new to SharePoint. I only explored SharePoint Office 365 (SharePoint Online) so I'm not familiar with the server-side of it. I'm using SharePoint 2010. I've installed it in a server along with SQL Server 2008 R2 (so this server is the SharePoint server and the database server). I've configured it as a standalone (which is I'm not sure if right). I have another server for Active Directory Users and the SharePoint/Database server is a member of it's domain. How can I add users from Active Directory to be able to access the Central Administration and the site I'm going to build with the SharePoint/Database server? Please help me as I'm a beginner here. Thanks a lot in advance!
Login using the user which you used to install the Sharepoint 2010.
It will become your System Account . Then add other AD users to the CA site. and provide them appropriate permissions as per your requirements
Also add ad users to the site collection administrators for the other site you want to access .
Add them as a Site collection administrators for that site from Central administration
then log into that site :- goto site actions > site setting > People and Group
Here you can add the users in a group from AD users and provide them appropriate permissions
Is it wise to use Domain Administrator as a SQL Windows Authentication log-in?
No. Local admin, perhaps, yes: never domain admin
For example, xp_cmdshell would allow complete control over AD and your environment. CLR code could do the same. Although these are disabled by default, you can't rely on that to protect your entire network.
Edit:
Logging in as a user as domain admin is no different to using Exchange or similar with the same acount. For SQL Server. no extra rights are conferred or implied because all permissions are defined within SQL Server.
So if you only have a "SQL Server Admin" group as sysadmin, and the domain and local admins are not in this group or set up as logins, then they get normal user rights as per their login. Or they can't even connect.
Of course, as domain or enterprise admins they could just add themselves to the "SQL Server Admin" group... but this requires an extra step and restricts your sysadmin to the correct admin group.
After all, you wouldn't let me as SQL God near your Exchange server...
I think some of the posts have assumed you mean to run the SQL Server service under a domain administrator account (which I agree, would be a security hole), but as you have said in your clarification, it is just to log in to do stuff against the database, I don't see a problem with it....As long as the user in question (I'm guessing it's you here), knows not to drop the production database etc.!
Certain things you need to do against an install require DBA priveleges, if you acquire those by being a domain admin, then what difference does it make?
a. If you have no security problems than - it doesn't matter.
b. if you are connected to the internet, you shouldn't. someone can attack your domain using holes in sql code if the app you're using uses the domain admin authentication. or if someone get access to your administration machine.
c. there is no linkage between domain admin and sql server admin - so why do it ?
Just to be clear - It is not wise !
In my opinion, I wouldn't use an Administrator account for anything management related (that's my Linux background telling me that root accounts shouldn't be used).
It depends a lot about - well - your size and security practices. It does show a security risk, but whethe rit is wise o wnot depends on the rest of the setup.