Viewing 15 posts - 1,816 through 1,830 (of 6,041 total)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 18, 2017 at 12:54 pm
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 18, 2017 at 9:27 am
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 18, 2017 at 9:23 am
Yes, SQL Azure's contained database model will take some getting used to, but the issue isn't just about security, there are technical reasons why this is done. In a cloud...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 18, 2017 at 9:16 am
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 18, 2017 at 8:49 am
I once inadvertently coded an update script that looked something like this:
SET @User = 1234;
UPDATE VeryBigTable
SET Status = 0
WHERE User = User;
From...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 18, 2017 at 7:46 am
Assuming each query has the same parameters and the data was static between executions, I would expect the number of page reads and the execution plan to be the same....
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 18, 2017 at 7:11 am
Hi Ben,
Using the following Google search expression, I was able to find the diagram you're looking for or at least something similar. It looks like there may be several...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 17, 2017 at 3:47 pm
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 17, 2017 at 12:37 pm
OK, I now see this was entered under 'Articles Requested'. I thought it was a general question. Offhand, I don't know of any limitations that TDE would place on other...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 17, 2017 at 8:53 am
Generally speaking, there is no good reason to repeatedly shrink a database on a schedule. What this does is reduce the physical size of the data file on disk. The...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 17, 2017 at 8:17 am
I am currently working on design phase of an integration of a new CRM system...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 17, 2017 at 7:59 am
In the case of a distributed database environment, like retail point of sale, I'd use a composite key like StoreID + TransactionID before I would resort to using GUIDs. So...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 17, 2017 at 7:48 am
This is an old thread, but
1. So the files do not become further corrupt, make a backup copy of the .mdf data and .ldf log files. This files should...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 17, 2017 at 7:38 am
I'm not seeing a link the original article, so I'm not sure about the question. However, regarding the question of using TDE with database Stretching, I don't see why it...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
January 17, 2017 at 7:14 am
Viewing 15 posts - 1,816 through 1,830 (of 6,041 total)