[PL] EXPRESS’owe instalacje (cz.11) – SQL Server 2016 CTP 3.0

Najnowsza wersja SQL Server 2016 CTP (Community Technology Preview) 3.0 już jest dostępna  – od kilku dni zaledwie. Wersji Express dostępnej w ramach standardowej istalacji jeszcze nie ma, ale dla każdego chętnego dostęp do niej się znajdzie. Data wydania wersji RT nie jest jeszcze bliżej znana, a biorąc pod uwagę różnice jakie się pojawiały pomiędzy wersjami CTP: 2.1 > 2.2 > 2.3 > 2.4 i wreszcie 3.0 może warto spokojnie poczekać.

Aby dostać się do wersji Express instalacji SQL Server 2016 CTP 3.0 należy udać się na stronę z wersją evaluacyjną (lub skorzystać z subsktypcji MSDN jeżeli się takową posiada). 

image

Rys.01 | Strona z powitaniem i linkami do wielu źródeł wiedzy.

 

image

Rys.02 | Strona gdzie możemy pobrać obraz ISO (choć nie tylko).

 

Captura_SQLServer2016CTP3_express01

Rys.03 | Z rozwijalnej listy możemy wybrac wersję Evaluation albo Express

 

Captura_SQLServer2016CTP3_express02

Rys.04 | Po wybraniu wersji express dostajemy do przeczytania Microsoft Pre-Release Software License Terms for Microsoft SQL Server 2016 Express Community Technology Preview 3 (CTP)

 

Captura_SQLServer2016CTP3_express03

Rys.05 | Standardowy (już od wersji 2014) ekran sprawdzający potrzebne biblioteki, albo oprogramowanie wspomagające.

 

Captura_SQLServer2016CTP3_express04

Rys.06 | Pierwsze podsumowanie spełnienia reguł wymaganych dla instalacji aplikacji.

 

Captura_SQLServer2016CTP3_express05

Rys.07 | Tutaj wybieramy odpowiednią dla nas wersję – w tym wypadku nową instalację SQL Server 2016 CTP3 – oprogramowania

 

Captura_SQLServer2016CTP3_express06

Rys.08 | Domyślny wybór SQL Server Feature Installation jest w zasadzie jedynym rozsądnym – bo jako administratorzy musimy i chcemy mieć kontrolę nad tym co i jak się instaluje.

 

Captura_SQLServer2016CTP3_express07

Rys.09 | Teraz pozostaje nam wybranie jakie funkcjonalności dla naszej nowej instancji chemy zainstalować. Jeżeli założymy, że interesuje nas wersja advanced, to wybierzemy wszystko. Oczywiście w produkcyjnym srodowisku powinniśmy zaistalować tylko to co jest nam potrzebne.

 

Captura_SQLServer2016CTP3_express08

Rys.10 | Po wybraniu interesujących nas opcji, przede wszystkim wybieramy root instance directory (który u mnie zawsze NIE JEST na dysku systemowym). Możemy się tez dowiedziec ile nasza instalacja zajmie nam miejsca – w tym wypadku już na dwóch dyskach.

 

Captura_SQLServer2016CTP3_express09

Rys.11 | Tutaj nam sie odzywa nowość. Poniewaz zanaczyliśmy w funkcjnalnościach, że chcemy mieć Advanced Analytisc Extensions (czyli w skrócie obsługe języka R dla potrzeb analitycznych) musimy pamiętać, że aby skorzystać z tej funkcjonalności niezbędne będzie doinstalowanie środowiska dla platformy R, po zainstalowaniu samego SQL Server.

 

Captura_SQLServer2016CTP3_express10

Rys.12 | Biorąc pod uwagę ilość instancji na maszynie, jak zawsze używam specyficznych nazw dla poszczególnych instancji. SQL Server 2016 Express CTP3 nazywa się więc INUKAI

 

Captura_SQLServer2016CTP3_express11

Rys.13 | Odpowiednie, osobne konta (w produkcji pobrane z Active Directory, turaj z zasobów lokalnych) dla Sinika oraz Reporting Services. Pojawia się też nowe konto SQL Server Launchpad (choć to nie jedyne nowe konto), w którym niestety nic nie możemy zmienić – a zwłaszcza ustawień startu. Można to oczywiście obejść przez przystawkę services.msc po instalacji. Nie zajrzałem tutaj w Collation, więc sposób sortowania może mnie potem zaskoczyć.

 

Captura_SQLServer2016CTP3_express12

Rys.14 | Dodanie kont administrujących… (domyślnie żadne nie jest dodane, co uniemożliwi nam łatwe dostanie się do instancji po zainstalowaniu)

 

Captura_SQLServer2016CTP3_express13

Rys.15 | Dodaję więc standardowo konto swoje własne i konto administratora instancji.

 

Captura_SQLServer2016CTP3_express14

Rys.16 | Na następnym ekranie podajemy ścieżki do katalogów w jakich trzymane będą poszczególne pliki. Dla wersji Express nie ma to aż tak dużego znaczenia, ale przy każdej innej już warto się nad rozmieszczeniem zastanowić.

 

Captura_SQLServer2016CTP3_express15

Rys.17 | Nowość w SQL Server 2016 – czyli więcej ustawień dla TempDB. Możemy tu wybrać od razu: ile ma być plików TempDB, jaką mają mieć wielkość początkową i przyrost automatyczny, oraz oczywiście lokalizację dla plików.

 

Captura_SQLServer2016CTP3_express16

Rys.18 | Jeżeli ścieżka ma być inna, trzeba ja dodać ręcznie…

 

Captura_SQLServer2016CTP3_express17

Rys.19 | A następnie sprawdzić czy ścieżka dla plików log dla bazy TempDB ma być taka sama czy też inna.

 

Captura_SQLServer2016CTP3_express18

Rys.20 | User Instances – czyli LocalDB

 

Captura_SQLServer2016CTP3_express19

Rys.21 | Standardowa instalacja dla Reporting Services pozwoli nam zainstalowanie i domyślną konfigurację.

 

Captura_SQLServer2016CTP3_express20

Rys.22 | Podsumowanie instalacji – warto od razu ten plik skopiować, aby zrobić z niego (albo wprost go zastosować jako) dokumentację po-instalacyjną

 

Captura_SQLServer2016CTP3_express21

Rys.21 | Instalacja…

 

Captura_SQLServer2016CTP3_express22

Rys.24 | …instalacja…

 

Captura_SQLServer2016CTP3_express23

Rys.25 | … i końcowa instalacja

 

Captura_SQLServer2016CTP3_express24

Rys.26 | Niestety w przeciwieństwie do poprzednich instalacji nie dostajemy podsumowania w pustym polu ze szczegółami

 

Captura_SQLServer2016CTP3_express25

Rys.27 | Dodatkowy serwis jaki możemy znaleźć w serwisach: SQL Server Telemetry Services (o nim w innym poście będzie trochę wiecej)

 

Captura_SQLServer2016CTP3_express26

Rys.28 | I wspomniany wcześniej SQL Server Launchpad – który jest niezbędny do pracy z analityką (o czym ów serwis nas informuje)

 

 

LINKI:

  • strona z powitaniem
  • strona z plikiem ISO
  • [EN] New Virtual Box release available (v.4.3.4)

    Ho Ho Ho! Two weeks ago Oracle released new version of VirtualBox hypervisor. Now it’s time to play. For many reasons this is my favourite environment now, and I’m happy to share information what’s happened with this version. You can download different versions of VirtualBox installation files from the site:

    Of course You should remember about very cool extension pack for VirtualBox:

    • VirtualBox 4.3.4 Oracle VM VirtualBox Extension Pack All supported platforms
      Support for USB 2.0 devices, VirtualBox RDP and PXE boot for Intel cards.

    After upgrading VirtualBox environment and extention pack, remember to update extension packs version on each virtual machines in Your environment. What happened with new version? Lets look for changelog (copied from site):

    In this is a maintenance release. The following items were fixed and/or added:

    • VMM: fix for a bug in the Local APIC emulation causing a BSOD when booting certain guests (4.3.0 regression; bug #12240)
    • VMM: fixed loading of saved states if VT-x/AMD-V was disabled (4.3.2 regression; bug #12291)
    • VMM: fixed single-stepping inside the guest for certain instructions (VT-x only; bug #10947)
    • VMM: fixed a performance issue involving APIC accesses after rebooting a VM (4.3.0 regression; VT-x only; bug #12296)
    • VMM: fixed TPR patching to be enabled for 32-bit guests even when the chosen guest type is 64-bit (4.3.0 regression; AMD-V only)
    • VMM: fixed occasional VINF_EM_TRIPLE_FAULT errors on hosts without the unrestricted guest execution feature (bug #12198)
    • GUI: don’t bother the user with the BPP warning if no Guest Additions are installed
    • GUI: fixed machine-window paint artifacts on VM reboot / guest-screen resize
    • GUI: make sure the assigned license and description are attached to the exported appliance
    • GUI: fixed bugs in close VM action restrictions handling (bug #12333)
    • GUI: fixed incorrect wizards text colors for some unusual look and feel styles (bug #11743)
    • GUI: should restore seamless mode as soon as possible after VM reboot or shutdown
    • GUI: fixes for medium enumeration
    • GUI: the OS X hot corners were not accessible while a VirtualBox VM is running (Mac OS X hosts only; bug #4139)
    • GUI: fixed an old bug which bared the host from cleanly shutdown / reboot if the VM selector window is open (Mac OS X hosts only; bug #8254)
    • Host-only Networking: fixed creating of host-only network interfaces (4.3.0 regression; bug #12182)
    • NAT: don’t run into an infinite loop in case the host cannot access any DNS server (4.3.0 regression; bug #12300)
    • NAT: don’t re-connect the cable if the DNS information changes and the cable was disconnected before (4.3.0 regression; bug #12225)
    • NAT: fixed several issues with automatically starting / terminating of NAT networks on VM start / stop and configuration changes
    • VBoxNetDHCP: don’t block prevent VBoxSVC from terminating (bug #12264)
    • 2D Video acceleration: fix crashes on presentation mode switches (bug #9194)
    • BusLogic: allow to run VMs with more than one BusLogic SCSI controller enabled
    • Keyboard: fixed a VM crash if a VM was resumed from a saved state where at least one key was pressed (bug #11289)
    • VBoxSVC: fixed a heap corruption under certain conditions (4.3.0 regression)
    • VBoxSVC: fixed a race leading to a hang during initialization (bug #12349)
    • OVF: fixed import logic for OVF appliances containing multiple VMs
    • OVF: improved logic for finding an appropriate image format during OVF import
    • API: block the removal of the current snapshot if it has child snapshots (only relevant for VMs without snapshottable hard disks, their presence always prevented removal), which resulted in VM configuration corruption
    • API: mark VM configurations with snapshots but without current snapshot as inaccessible, as this combination is nonsense
    • API: fixed information for some automatically generated events (only with XPCOM, Windows host was not affected), which caused errors when getting some of the attributes over the webservice (bug#12379)
    • SDK: extended the functionality coverage for the C bindings
    • Guest Control: various bug fixes and improved VBoxManage help (bugs #8072, #11044, #12336, #12338, #12346, #12371)
    • Windows hosts: another attempt to fix the massive DPC latency (bug #6242)
    • Windows host installer: make registering file extensions optional, contributed by Tal Aloni (bug #8009)
    • Mac OS X hosts: properly sign the kernel extensions for Mavericks hosts (bug #12256)
    • Mac OS X hosts: fixed a bug where the VirtualBox dock icon was not properly removed from the dock after a VM terminated preventing Mavericks hosts from shutting down (bug #12241)
    • Mac OS X hosts: fixed minor installer issue (bug #12275)
    • Linux hosts / guests: Linux 3.13 compile fixes (bug #12358)
    • Linux guests: build the vboxvideo kernel module correctly on OL/RHEL 6.1 guests (bug #11996)
    • Linux guests: make 3D work on Slackware 14.1 (bug #12320 comments 3 and 4)
    • Guest Additions/3D: fixed an occasional dead-lock (bug #12319)
    • Windows Additions/3D: fixed possible memory leaking (bug #12228)
    • Windows Additions/XPDM: use separate tables containing valid video modes for each virtual monitor
    • Windows Additions: fixed automatic logins for Vista and newer Windows guests (bug #12332)

    Download. Play. Enjoy.

    [EN] SQL Server 2008 R2 Service Pack 2 is available

    LOGO__SQLServer2008R2Sp2Just about two weeks ago (exactly on 26th July) Microsoft has released a long awaited Service pack 2 for SQL Server 2008 R2. Generally as almost always there are three parts of those packages:

    • for SQL Server (Standard, Enterprise, DataCenter and so on)
    • for SQL Express Edition
    • for Feature Packs

    In this post I will share some basic info about service pack for engines. SP2 contains changes from SP1 and Cumulative Updates from 1 to 5. after Depends of version of Your software You can use different software:

    FOR SQL SERVER

    This service pack {build number: 10.50.4000.0} KB2630458 is available for three platforms: x86 {241 MB LINK}, x64 {352 MB LINK} and for Itanium {337 MB LINK}.  Full information and more links You can find on SP2 page HERE.

    FOR SQL SERVER EXPRESS

    Another pack, but the same build number and KB number (but different SITE). Based on public information most important Key Features in this service pack looks pretty well:

    • Supports stored procedures, triggers, functions, and views
    • Store all kinds of business data with native support for relational data, XML, FILESTREAM and spatial data
    • Improved performance, usability, visualization, in addition to integration with the Microsoft 2007 Office System in SQL Server Reporting Services
    • Simplify development efforts by leveraging existing T-SQL skills, ADO.NET Entity Framework and LINQ
    • Closely integrated with Visual Studio and Visual Web Developer

    Software are available in more than three (ha!) versions: SQLSRVEXP_32 {runtime 87MB LINK}; SQL Server Express {x86 110MB LINK and x64 122MB LINK}; SQL Server with Advanced Tools {x86 894MB LINK and x64 1008MB LINK}; SQL Server Express Edition With Tools {x86 318MB LINK and x64 340MB LINK}; SQL Server Management Studio only {x86 158MB LINK and x64 161MB LINK}.

    It doesn’t matter which version You will use. Before You start updating,

    read SQL Server 2008 R2 SP2 Release Notes, then download a right file (look above),

    backup your environment, test in dev zone and at last – update.

    For additional information which bugs was solved in Service Pack 2 for SQL Server 2008 R2 look below (and/or on page):

    Fixed issues:

    VSTS BUG: 820875 922578
    FIX: Lots of messages that have message ID 19030 and message ID 19031 are logged in SQL Server 2005, SQL Server 2008 or SQL Server 2008 R2 Errorlog file when you use SQL Server Profile in SQL Server 2005, in SQL Server 2008 or in SQL Server 2008 R2

    VSTS BUG: 728527
    2216456
    FIX: SQL Server 2008 Service Pack 2 and SQL Server 2008 R2 Service Pack 2 enhancements to the "Operation has been cancelled" error message text in Analysis Services

    VSTS BUG: 820858
    2550375
    FIX: Deadlock might occur in sys.dm_database_encryption_keys DMV in SQL Server 2008 R2 when you run log shipping from many databases to one secondary server

    VSTS BUG: 820878
    2565683
    FIX: You may receive incorrect results when you run a complex query that contains aggregates functions, join functions, and distinct functions in subqueries in a SQL Server 2008 or SQL Server 2008 R2 environment

    VSTS BUG: 820756
    2588050
    FIX: Slipstream installation of a SQL Server 2008 or SQL Server 2008 R2 service pack fails when you add new features to the SQL instance if database engine is installed

    VSTS BUG: 901689
    2653857
    FIX: You cannot connect to SQL Server by using JDBC Driver for SQL Server after you upgrade to JRE 6 update 29 or a later version

    Additional fixed issues:

    VSTS BUG: 820845
    The fix is related to usage of BindParameter method and the reference of long type parameters that are used by this method.

    VSTS BUG: 852397
    The fix is to update UpgradeIncompleteFeatureConfigEventHandler.cs to include RebuildDatabase scenario when you reset ConfigurationState.

    VSTS BUG: 887672
    For document libraries with the “Opening Documents in the Browser” setting set to “Open in the client application” GetSnapshot.exe ignore the configuration and always displays the workbook by using Excel Services as if the setting was “Open in the browser”.

    VSTS BUG: 820805
    On a Russian Localized build of the Reporting Services Configuration Manager, Execution Account information that is contained clipped strings.

    VSTS BUG: 718430
    The ExpectedCount and ExpectedElapsedMs usage counts are updated to reflect the actual counts respectively.

    VSTS BUG: 737914
    Fixes an issue in which SQL Server 2008 R2 Analysis Services crashes during the database synchronization.

    VSTS BUG: 788389
    Trace flag 1264 is removed and so that the process name is collected by default in non-yielding scenario dumps. The number of thread records in non-yielding scenario dump files is increased from 1K to 16K.

    VSTS BUG: 820762
    SQL Server 2008 R2 changes the FireAgain parameter to True if an event should be logged. However, after some codes are removed by mistake, some logs are missing because of the FireAgain parameter is only determined by the external event listener. After you apply this hotfix, the issue is resolved.

    VSTS BUG: 820764
    Consider the following scenario. You have indexed view projects columns from base and non-base tables in SQL Server 2008 R2. A column from the non-base table has the same order id and type as a column of the base table. In this scenario, SQL Server 2008 R2 switches the partitions. After you apply the hotfix, SQL Server 2008 R2 experiences an error instead of switches the partitions.

    VSTS BUG: 820792
    Fixes an issue in which an object that is allocated on a SOS_Task PMO could be also used by other TASK which has a different life span. This service pack uses the correct PMO for allocating the object.

    VSTS BUG: 820796
    After you apply the hotfix, the optimizer understands that CRYPT_GEN_RANDOM can return different outputs for the same input.

    VSTS BUG: 820859
    Fixes an issue in which an incorrect value is returned when you run the SCOPE_IDENTITY().

    VSTS BUG: 820864
    Fixes an issue in which the SQL Server 2008 R2 setup crashes when you install SxS with Shiloh OLAP SP3a. This issue occurs because the Shiloh OLAP SP3a incorrectly writes the version registry key as "Service Pack 3.0."

    VSTS BUG: 820873
    Fixes an issue in which an incorrect CPU time is reported by sys.dm_exec_query_stats when parallel query plans are involved.

    VSTS BUG: 820880
    Fixes an issue that occurs when internal asynchronous file reading buffers are splitting the multi-character column delimiter in two parts. The fix is to correctly reset the current parsing pointer after buffers are switched.

    VSTS BUG: 847805
    The fix will only use the synchronization if the SQLWixCompilerExtension operation runs in candle.

    VSTS BUG: 890643
    This fix changes the HierarchyGet operation to avoid a certain code path for the explicit cap that only applies to the derived part of the hierarchy. The update is a one-line update that is low risk.

    VSTS BUG: 731796
    Fixes an issue in which you receive errors in a statement when purging from snapshots.notable_query_text.

    VSTS BUG: 820829
    Bad GUID values parsed from flat files could cause errors. The fix is to fall back into a truncation mode if the source buffer is bigger than max size of a GUID string.