New answers tagged configuration
The answer to this question varies depending on what database engine backend you're using. If you're wildly unfamiliar with all of them, I really recommend that you use TokuDB, because it's entirely self-configuring with no modifications necessary out of the box. I use MariaDB (MySQL clone) with Aria tables. My configuration would be totally, and ...
The MongoDB server actually does not search any locations for config files, and there is (as at MongoDB 3.2) no way to specify multiple config files or include config file fragments. There was a feature suggestion for includes discussed (see: SERVER-14911 in the MongoDB issue tracker), but it was decided that includes are not part of standard YAML and ...
The issue is probably due to this line: host all all 192.168.0.0/24 md5 This (the 24) basically tells Postgres to allow connections from any machine that has IP of the form: 192.168.0.x. So, your 192.168.10.195 does not match the criteria. You can replace it with: host all all 192.168.0.0/16 md5 -- any 192.168.x.x or host ...
If you look at Maximum Capacity Specifications for SQL Server, you will see that the maximum size for transaction log is 2 TB: SQL Server Database | Maximum sizes/numbers | Maximum sizes/numbers Engine object | SQL Server (32-bit) | SQL Server (64-bit) ... | ... | ... File size (log) | 2 terabytes ...
I would like to Add to 'Kin's answer and add that if you are running a 32 Bit office products and there for a 32 bit version of AccessDatabaseEngine which is what is used for communications to office products (Excel) Then you may have this issue, however if you change to 64 bit this should disappear. (and Ace will appear on your linked servers.)
Naga this error would be where I would start looking SQLServer Error: 27, Registry information is corrupt or missing.Make sure the provider installed and registered correctly. [SQLSTATE 08001] If you are able to a repair of the installation should resolve this.
Set the SQL Agent service to Automatic(Delayed). The first thing it will do is try to connect to SQL Server, and if SQL Server hasn't finished starting yet, SQL Agent can fail. Delaying the start for SQL Agent will give SQL Server the chance to finish.
Make sure the SQL Agent service user (the one in services.msc) is a valid login on the SQL Server instance. If it is, look for 18456 errors in the SQL log to see why that login can't log in. Specific details in the MSDN Select an Account for the SQL Server Agent Service article
Its a weird quirk of the Postgres clients that the ones that are remote or in scripts typically connect to the server using its address and are then authenticated by password but when you connect from the same machine via the command line client then it tries to use peer authentication and you get that error. I found from this answer that you can fix it by ...
You have to change the service account in SQL Server Configuration Manager in order to have all required permissions applied to the service account. Open Configuration Manager, select SQL Server Services in the treeview on the left, then open the properties window of the desired SQL Server instance. Set the service account as follows: Then open file ...
I liked it and have not seen it being removed anywhere so far. I used PowerShell DSC since the beta and it's great but it is no replacement for PBM. DSC is great for enforcing system states and some SQL states. I can use it to roll out automated testing environments and ensure all the domain membership, firewalls, users, restored databases, masked data, ...
Top 50 recent answers are included