Tag Info

New answers tagged

3

According to Paul Randal the number of tempdb files should be: equal to the number of CPU cores for 8 or less cores 1/4 to 1/2 of CPU cores for more than 8 cores I think it's a great news that Microsoft finally changed this default setting. The previous one was really bad - it caused problems with latch contention. Paul Randal's article on the topic


0

I know that only root can write to /var/log ... You can change that. As root user in the shell: mkdir /var/log/postgresql chmod 0600 /var/log/postgresql chown postgres:postgres /var/log/postgresql And in postgresql.conf: log_destination = 'stderr' logging_collector = on log_directory = '/var/log/postgresql' log_filename = ...


0

You don't edit the path. I solved the problem by the command: mongod --dbpath /data/mongo


0

Yes it is possible to set one of the instances to run on port 1433. It is also safe as the dynamic ports will be set in the range of 49152 and 65535 as stated above. You use the configuration manager to set one of the instances to start at port 1433 (clearing the configuration for the dynamic port) and it will run on that port afterwards.


5

When a SQL Server named instance configured with dynamic port is started, the dynamic port is provided by windows. The dynamic port range is outside the range of well-known static ports, where port 1433 resides. The dynamic port range is between 49152 and 65535, as documented here. At subsequent startups, the instances reuse the same dynamic port used ...


3

Open SQL Server Configuration Manager In the SQL Server Services pane, locate the instance that has the problem Right-click that instance and select Properties On the Startup Parameters tab, type -f, click Add, then click Apply Right-click that instance and select Start (or Restart) This will start the instance in minimal configuration mode (single user, ...


1

I ran into a similar issue and found it to be a misconfigured mongod.conf file in my case. It could also be the permissions on the new directory are not set properly. chown -R mongod:mongod <directory name> was how I ensured access (and of course the chmod 600 <dir> as well). Lastly, run an ls -Z to ensure the context is correct. I just ...


0

600 inserts/sec is more than out-of-the-box MySQL can do. You have done some tuning; more is possible. innodb_flush_log_at_trx_commit = 1 is the default, but it incurs a write after every transaction. =2 can be significantly faster. Batching inserts, if feasible for your application, can speed up INSERTs 10-fold. How many secondary indexes are there? ...


-1

Restart the postgres server from the terminal for ubuntu sudo service postgresql restart then it will dispay the results of the cause for failure e.g 2015-05-08 17:33:46 EAT FATAL: private key file "/etc/ssl/private/ssl-cert-snakeoil.key" has group or world access 2015-05-08 17:33:46 EAT DETAIL: File must be owned by the database user or root, must have ...


0

MyISAM is faster than innoDB in insertion and that is because it relies on OS to write data to disk while innoDB insures final disk write (fsync()). moreover, innodb MVCC feature reduces the write speed. If the little delay in write is not a problem, stick to innoDB. you don't want to face lots of table crash or long table locks while your table face read ...


1

Your shell PATH environment variable is not pointing to your folder /usr/lib/postgresql/9.4/bin/. In order to do this, use the command PATH="/usr/lib/postgresql/9.4/bin/:$PATH". If you want to automate this, you can add this line in your shell config file (ie. ~/.bashrc) with this : echo 'PATH="/usr/lib/postgresql/9.4/bin/:$PATH"' > ~/.bashrc.


2

I checked this out and the latest available standalone for SQL Server Management Studio is a 2008 version here. Thanks to @AaronBertand, the process of obtaining the SQL Server Management Studio 2014 involves clicking the download button for the full SQL Server Express 2014 and then you will be offered a choice of only downloading the Studio (see here - ...



Top 50 recent answers are included