Tag Info

Hot answers tagged

3

In my opinion putting the tempdb in the SSD drive without looking at the performance stats is the wrong way to go. SSD drives have high cost/GB and are a premium resource that should be used in the best possible way. You will probably get better performance moving the most used database files to the SSD, given that you already have broken your database into ...


3

Think of your database like a bucket. The ALLOCATED space is how big the bucket is, i.e. how much data it can hold. The USED space is how much water/data is actually inside the bucket. When the water gets to the top of the bucket, you need to make the bucket bigger by allocating more space.


3

Method 1: Easy way The Best way that i am using as of now is ola hallengren's SQL server Maintenance solution for SQL Server Integrity Check. Within this solution it gives you an option of storing the output or logging it to a table as per you're convenience: LogToTable Log commands to the table dbo.CommandLog. Please read the complete web link as ...


3

Why do you think clustering will help performance? There is no such thing as active/active anyway - a failover cluster exists to provide a fallback so that the database can continue running if the hardware fails (the database is only ever active on one of the cluster nodes at any one time). Clustering <> load balancing. If you mean splitting up the data ...


2

You can also look at the application event log. For SQL 2008 R2 instances, the event ID to filter on would be 8957 (at least for success codes).


2

I would re-write the whole proc something like this..... ALTER PROCEDURE Member_WS @Program int = NULL, @Card nvarchar(30) = '', @Account nvarchar(128) ='', @Member bigint = NULL, @Email nvarchar(256) ='', @Phone nvarchar(20) ='', @ResponseType ...


2

There was a bug with commit_delay in PostgreSQL 9.4.X. It was just fixed, and the fix will appear in version 9.4.5. See the thread on the PostgreSQL mailing list: http://www.postgresql.org/message-id/CACKh8C-tDjQUceMQeG3BUSHS5AA35SjvCD6HgRm-Vj7x5rXmeQ@mail.gmail.com


1

Perhaps you should dump the users and load the users into the VM Here is my post : Export all MySQL users After running the code in it and saving it to a file called MyDatabaseUSers.sql, you log into mysql on the VM and run this: mysql> source MyDatabaseUSers.sql This will create all the users with the same grants and passwords. Don't worry: ...


1

Judging by the answer you gave in response to @Ozzie, I'm not sure you can do what you want. You can export the metadata of an 11gR2 database using expdp (Data Pump) and the METADATA_ONLY flag. See http://docs.oracle.com/cd/E11882_01/server.112/e22490/dp_export.htm This will export the structure of your data. This won't include redologs, controlfiles, ...


1

I wouldn't expect a copy operation to increase file sizes unless the file size was too small to begin with. SQL Server will first use unallocated space within data files before growing the file. Similarly, if the log file is large enough for the operation, that file shouldn't grow either. Also regarding log space usage, some operations can be minimally ...


1

Per the PostgreSQL tablespaces documentation: If a database is created without specifying a tablespace for it, it uses the same tablespace as the template database it is copied from. Per the CREATE DATABASE documentation: By default, the new database will be created by cloning the standard system database template1. You could either alter the ...


1

When talking about memory storage, the Hotel analogy also works well. But in this kind of hotel only one person is allowed in a room at a time; a man or a woman. This represents bit data. Ones and zeros. The max capacity of the hotel is 512 people. Before your hotel opens you decide to allocate only half of your rooms for guests. The allocated space is ...


1

What you described here is absolutely normal and intended. This feature is called a global database link: http://docs.oracle.com/cd/E24693_01/server.11203/e17120/ds_concepts002.htm#i1007888 It is a "side effect" when for example Oracle Internet Directory is in use, I have seen this at a few companies who have a lot of databases. More and better ...


1

Version store basically cause from long running transaction or high transaction throughput. You need to look for the queries which are causing this. Other than that version store is used in following conditions: Row version which are generated by data modification transactions for features (MARS, online indexes, AFTER trigger etc) Row version which are ...



Only top voted, non community-wiki answers of a minimum length are eligible