Amazon has launched their AWS Directory Service. This is used to create new or use existing company Active Directory which allowed users in your company to access AWS.
Quite a good article about how to find oiut which table is corrupt ion your SQL Server database
Great news for those affected by the CryptoLocker virus.
A very scary state of affairs in that the exploit requires no prompting – all that is required is a rogue “femtocell” (basically a small phone base station) that then gives access to the management functions that mobile phone companies use to push out “over the air” changes.
THE Australian Defence Force’s optometry service provider has been sacked after sending patients’ medical records offshore.
OPSM’s parent company Luxottica Retail Australia yesterday lost its $33.5 million contract with the ADF after sending Defence personnel’s optical claims information overseas for processing.
We were dealing with a client who had a very large database that was out growing their disk space. Initial plan was to shrink the database to regain the almost 18GB of space that was not used anymore. Started the shrink and found it was taking a very long time to complete. Even worse when it completed performance was worse than before – even though the database was now smaller. Strange!
It was at this moment that something snagged in my brain and I remembered something I had read about NEVER having AutoShrink and ONLY AS A LAST RESORT do a shrink. I found the article and thought I would share it here:
From SQL Server Shrink
Shrinking of data files should be performed even more rarely, if at all. Here’s why – data file shrink causes *massive* index fragmentation.
The only way to remove index fragmentation without causing data file growth again is to use DBCC INDEXDEFRAG or ALTER INDEX … REORGANIZE. These commands only require a single 8KB page of extra space, instead of needing to build a whole new index in the case of an index rebuild operation.
Valuable lesson learned!
Big thanks to Ben Armstrong for this one.
Some very good advice about working out what your baseline network should look like and then limit the traffic to just above this level so that when you do get hit by some sort of malicious traffic then it does not affect your network too much).
Important All future security and nonsecurity updates for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 require this update to be installed. We recommend that you install this update on your Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2-based computer in order to receive continued future updates.
What this means is that unless you get this patch onto your client machines they will be unable to download and install security updates from May onwards… therefore you NEED TO GET THIS TESTED AND DEPLOYED OUT SOONER THAN LATER.