Установка сервера «1С:Предприятия» 8.3 на MS SQL Server 2012 / 2008 (R2)
Список версий Microsoft SQL Server
1С 8.3 : Установка 1С 8.x на MS SQL Server 2008 R2 Express
В свое время из-за немного громоздкой политики по выпуску обновлений для Microsoft SQL Server путался какой же из дистриубтивов нужно установить и откуда его скачать. Углубившись в данную тематику, в интернете нашел замечательные систематизирующие ресусры, которые отвечали на мои вопросы они приведены в начале статьи. Github версия в формате markdown на английском языке: SHA1 хэш можно легко получить с помощью встроенной Windows утилиты certutil. Так выглядит результат выполнения запроса SELECT VERSION для актуальной версии SQL Server vNext Developer Edition:. Последние обновления и фиксы: Так выглядит результат выполнения запроса SELECT VERSION для актуальной версии SQL Server Developer Edition:. GitHub обновляется даже зачастую оперативнее Если уж надо на русском, то можно сюда. На хабре попытаюсь на выходных обновить, но пол года назад у меня не получилось — сам документ в формате markdown не корректно парсился при обновлении статьи скорее всего из-за его размера. Вроде хабр съел то наконец разметку, правда пришлось часть ранних билдов из версии года удалить не страшно, так как она уже год как не поддерживается официально , но зато все осталное все таки обновилось. Не могли бы подробнее описать саму проблему? Какая версия SP1? По какой ссылке не можете скачать? И на каком ресурсе данная проблема всплывает с года? Странно, использовал данный загрузчик неоднократно на разных компьютерах, все скачиловась и проверялось без проблем. На всякий случай — вдруг вам будет полезно в будущем, прямые ссылки для загрузки любой версии SQL Server доступны на Github актуализируются максимально оперативно в случае выхода обновлений SQL Server, обычно в течении суток , либо как альтернаитва у меня расшарена папка на Яндекс. Только полноправные пользователи могут оставлять комментарии. TM Feed Хабрахабр Geektimes Тостер Мой круг Фрилансим. Хабрахабр Публикации Пользователи Хабы Компании Песочница. Надеюсь собранная информация будет полезна не только мне. Полный список инструментов и утилит для Microsoft SQL Server утилит и инструментов Полный список флагов трассировки Microsoft SQL Server флага трассировки на текущий момент Разнообразие версий Microsoft SQL Server и какая из них последняя? Next Полный список расширений для SQL Server Management Studio SSMS 29 аддонов на текущий момент Список полезных ресурсов по Microsoft SQL Server более полезных ресурсов 10 причин почему именно сейчас стоит попробовать Microsoft SQL Server Заголовки: Часто используемые термины и акронимы Какие самые последние обновления доступны для SQL Server? Установочные файлы Microsoft SQL Server с прямыми ссылками на загрузку Версии SQL Server и уровни совместимости Общая информация по Service Pack Microsoft SQL Server VNext Builds Microsoft SQL Server Builds Microsoft SQL Server Builds Microsoft SQL Server Builds Microsoft SQL Server R2 Builds Microsoft SQL Server Builds Microsoft SQL Server Builds Microsoft SQL Server Builds Microsoft SQL Server 7. KB Наименование схем обновления для Microsoft SQL Server: KB Стандартная терминология, которая используется для описания обновлений ПО от Microsoft: KB SQL Server Updates от Brent Ozar с возможность подписки: RC Release Candidate версия-кандидат RDP Rapid Deployment Program RTM Released To Manufacturing RTW Release to Web TAP Technology Adoption Program SP Service Pack SU: Hotfix Обычно процедура установки SQL Server выглядит следующим образом: Устанавливается нужная вам стабильная версия на текущий момент рекомендуемые это или Затем устанавливается последний из доступных сервис паков Устанавливается последний накопительный пакет обнволений для устранения различного рода багов В случае необходимости для устранения конкретных проблем устанавливается нужный Hotfix Какие самые последние обновления доступны для SQL Server? Версия Последние обновления Номер сборки Дата релиза Начало цикла Поддержка Расширенная поддержка Другие обновления vNext Install vNext Other SQL vNext Updates Install SP1 then SP1 CU1 KB Например, для одного файла: Sphinx 70 70 SQL Server 6. Hydra 65 65 SQL Server 6. Общая информация по Service Pack Version Codename RTM no SP SP1 SP2 SP3 SP4 SQL Server vNext vNext Microsoft SQL Server vNext CTP1. Developer Edition bit on Windows … Последние обновления и фиксы: Microsoft SQL Server SP1-CU1 KB — Description of the security update for SQL Server CU Description of the security update for SQL Server GDR Microsoft SQL Server SP2-CU3 KB - Description of the security update for SQL Server Service Pack 2 CU: November 8, Description of the security update for SQL Server Service Pack 1 CU: Error when your stored procedure calls another stored procedure on a linked server in SQL Server Description of the security update for SQL Server Service Pack 1 GDR: Description of the nonsecurity update for SQL Server Service Pack 1 GDR: July 14, Description of the security update for SQL Server QFE: Error when you execute parallel query that contains outer join operators in SQL Server Poor performance when a query contains table joins in SQL Server Unpivot Transformation task changes null to zero or empty strings in SSIS Deadlock cannot be resolved automatically when you run a SELECT query that can result in a parallel batch-mode scan AlwaysOn availability groups are reported as NOT SYNCHRONIZING Cannot show requested dialog after you connect to the latest SQL Database Update V12 preview with SQL Server Description of the security update for SQL Server QFE Description of the security update for SQL Server GDR: Description of the security update for SQL Server Service Pack 3 CU: Description of the security update for SQL Server Service Pack 3 GDR: Performance decrease when application with connection pooling frequently connects or disconnects in SQL Server Access violations when you use the FileTable feature in SQL Server Description of the security update for SQL Server Service Pack 2 QFE: Data loss in clustered index occurs when you run online build index in SQL Server Hotfix for SQL SP2 Description of the security update for SQL Server Service Pack 2 GDR: Description of the security update for SQL Server SP1 QFE: Description of the security update for SQL Server Service Pack 1 QFE Data loss in clustered index occurs when you run online build index in SQL Server Hotfix for SQL SP1 Component installation process fails after you install SQL Server SP1 Description of the security update for SQL Server SP1 GDR: Description of the security update for SQL Server Service Pack 1 GDR SSAS uses only 20 cores in SQL Server Business Intelligence Description of the security update for SQL Server R2 Service Pack 3 QFE: Description of the security update for SQL Server R2 Service Pack 3 GDR: Description of the security update for SQL Server R2 Service Pack 2 QFE: Description of the security update for SQL Server R2 Service Pack 2 QFE Description of the security update for SQL Server R2 Service Pack 2 GDR: Description of the security update for SQL Server R2 Service Pack 2 GDR Description of the security update for SQL Server R2 Service Pack 1 QFE: October 9, Access violation when you run DML statements against a table that has partitioned indexes in SQL Server R2 Slow performance when an AFTER trigger runs on a partitioned table in SQL Server R2 Database data files might be incorrectly marked as sparse in SQL Server R2 or in SQL Server even when the physical files are marked as not sparse in the file system Description of the security update for SQL Server R2 QFE: June 14, Non-yielding scheduler error when you run a query that uses a TVP in SQL Server or in SQL Server R2 if SQL Profiler or SQL Server Extended Events is used Description of the security update for SQL Server R2 GDR: Description of the security update for SQL Server Service Pack 4 QFE: Description of the security update for SQL Server Service Pack 4 GDR: Description of the security update for SQL Server Service Pack 3 QFE: Description of the security update for SQL Server SP3 QFE Error when you run the "dbcc shrinkfile" statement by using the logical name of a file in SQL Server R2 or SQL Server Description of the security update for SQL Server SP3 GDR The Reporting Services service stops unexpectedly after you apply SQL Server SP1 CU 7 or CU8 Error message when you perform a rolling upgrade in a SQL Server cluster: Server is in script upgrade mode. Only administrator can connect at this time. SQLState " Error message in SQL Server when you run an INSERT SELECT statement on a table You may receive incorrect results when you run a query that references three or more tables in the FROM clause in SQL Server A MERGE statement may not enforce a foreign key constraint when the statement updates a unique key column that is not part of a clustering key that has a single row as the update source in SQL Server Description of the security update for SQL Server Service Pack 4 QFE 9. SQL Server Agent job randomly stops when you schedule the job to run past midnight on specific days in SQL Server , in SQL Server or in SQL Server R2 9. Error when you use the ONLINE option to rebuild an index in SQL Server 9. June 14, 9. Error message when you add a subscription to a republisher that is in a merge publication in SQL Server October 13, 9. Error message when you run a query that contains duplicate join conditions in SQL Server The query processor could not produce a query plan" 9. The performance of database mirroring decreases when you run a database maintenance job that generates a large number of transaction log activities in SQL Server 9. Error message when you run the DBCC CHECKDB statement on a database in SQL Server February 10, 9. Error message when you run a distributed query in SQL Server 9. In SQL Server , the session that runs the TRUNCATE TABLE statement may stop responding, and you cannot end the session 9. An ongoing MS DTC transaction is orphaned in SQL Server 9. All the MDX queries that are running on an instance of SQL Server Analysis Services are canceled when you start or stop a SQL Server Profiler trace for the instance 9. The Replication Log Reader Agent may fail intermittently when a transactional replication synchronizes data in SQL Server 9. An access violation occurs when you update a table through a view by using a cursor in SQL Server 9. Error message when you synchronize the data of a merge replication in SQL Server Check the status values for detail. Error message when you run a query that uses a join condition in SQL Server Error message when you run a transaction from a remote server by using a linked server in SQL Server Error message when you run queries on a database that has the SNAPSHOT isolation level enabled in SQL Server A stored procedure cannot finish its execution in SQL Server 9. The change may be undone during the later synchronizations when you change an article on the subscriber in SQL Server 9. A query takes longer to finish in SQL Server than in SQL Server when you open a fast forward-only cursor for the query 9. Error messages when you delete some records of a table in a transaction or when you update some records of a table in a transaction in SQL Server You cannot cancel the query execution immediately if you open a fast forward-only cursor for the query in SQL Server 9. A federated database server stops responding when you run parallel queries on a multiprocessor computer that uses NUMA architecture in SQL Server 9. Conflicts are not logged when you use the Microsoft SQL Server Subscriber Always Wins Conflict Resolver for an article in a merge replication in Microsoft SQL Server 9. Some changes from subscribers who use SQL Server Compact Edition or Web synchronization are not uploaded to the publisher when you use the republishing model in a merge publication in Microsoft SQL Server 9. The performance of a query that performs an insert operation or an update operation is much slower in SQL Server SP2 than in earlier versions of SQL Server 9. You receive error when you run a complex query in SQL Server 9. Error message when you run a full-text query against a catalog in SQL Server The content index is corrupt. A SQL Server Agent job fails when you run the SQL Server Agent job in the context of a proxy account in SQL Server 9. Error message when you run a stored procedure that starts a transaction that contains a Transact-SQL statement in SQL Server Error message when the Distribution Agent tries to apply the snapshot to the subscriber in SQL Server The Distribution Agent may skip some rows when you configure a transactional replication that uses the "-SkipErrors" parameter in SQL Server 9. You may receive error messages when you try to log in to an instance of SQL Server and SQL Server handles many concurrent connections 9. Error message when you use a server-side cursor to run a large complex query in SQL Server You may receive more than , page faults when you try to back up a SQL Server database that contains hundreds of files and file groups 9. SQL Server system performance may be slow when you use a keyset-driven cursor to execute a FETCH statement 9. The SQL Server SqlCommandBuilder. DeriveParameters method returns an exception when the input parameter is a XML parameter that has an associated XSD from an SQL schema 9. The monitor server does not monitor all primary servers and secondary servers when you configure log shipping in SQL Server 9. When you run the "dbcc dbreindex" command or the "alter index" command, some transactions are not replicated to the subscribers in a transactional replication in SQL Server 9. Errors may be generated in the tempdb database when you create and then drop many temporary tables in SQL Server 9. Indexes may grow very large when you insert a row into a table and then update the same row in SQL Server 9. The internal deadlock monitor may not detect a deadlock between two or more sessions in SQL Server 9. When you start a merge agent, synchronization between the subscriber and the publisher takes a long time to be completed in SQL Server 9. You experience a slow uploading process if conflicts occur when many merge agents upload changes to the publishers at the same time in SQL Server 9. The merge agent fails and a "permission denied" error message is logged when you synchronize a SQL Server based merge publication 9. Error message when an ADO. NET-connected application tries to reuse a connection from the connection pool in SQL Server The merge agent does not use a specified custom user update to handle conflicting UPDATE statements in SQL Server 9. A SQL Server login may have more permissions when you log on to an instance of SQL Server 9. An incorrect result may appear in the subscribing database when you set database mirroring for a database and database failover occurs in SQL Server 9. The replication on the server does not work any longer when you manually fail over databases in SQL Server 9. You may receive an access violation error message when you run a SELECT query in SQL Server 9. You cannot restore the log backups on the mirror server after you remove database mirroring for the mirror database in SQL Server 9. Error message when you run certain queries or certain stored procedures in SQL Server A script task or a script component may not run correctly when you run an SSIS package in SQL Server build 9. August 14, 8. Description of the security update for Microsoft SQL Server Service Pack 4 QFE: April 10, 8. An access violation occurs when you run a DELETE statement or an UPDATE statement in the Itanium-based versions of SQL Server after you install security update MS 8. Description of the security update for SQL Server QFE and for MSDE February 10, 8. When you run the SPSBackup. Description of the security update for SQL Server QFE and MSDE July 8, 8. The SPACE function always returns one space in SQL Server if the SPACE function uses a collation that differs from the collation of the current database 8. The data on the publisher does not match the data on the subscriber when you synchronize a SQL Server Mobile Edition subscriber with a SQL Server "merge replication" publisher 8. The CPU utilization may suddenly increase to percent when there are many connections to an instance of SQL Server on a computer that has multiple processors 8. An access violation may occur when you try to log in to an instance of SQL Server 8. The foreign key that you created between two tables does not work after you run the CREATE INDEX statement in SQL Server 8. You may receive an assertion or database corruption may occur when you use the bcp utility or the "Bulk Insert" Transact-SQL command to import data in SQL Server 8. A hotfix for Microsoft SQL Server Service Pack 4 may not update all the necessary files on an xbased computer 8. In SQL Server , the synchronization process is slow, and the CPU usage is high on the computer that is configured as the Distributor 8. The merge agent fails intermittently when you use merge replication that uses a custom resolver after you install SQL Server Service Pack 4 8. CPU utilization may approach percent on a computer that is running SQL Server after you run the BACKUP DATABASE statement or the BACKUP LOG statement 8. Error messages when you try to update table rows or insert table rows into a table in SQL Server SQL Server stops responding when you cancel a query or when a query time-out occurs, and error messages are logged in the SQL Server error log file 8. Error message when you create a merge replication for tables that have computed columns in SQL Server Service Pack 4: You may experience one or more symptoms when you run a "CREATE INDEX" statement on an instance of SQL Server 8. You may receive inconsistent comparison results when you compare strings by using a width sensitive collation in SQL Server 8. The server stops responding, the performance is slow, and a time-out occurs in SQL Server 8. Error message when you schedule a Replication Merge Agent job to run after you install SQL Server Service Pack 4: The result may be sorted in the wrong order when you run a query that uses the ORDER BY clause to sort a column in a table in SQL Server 8. You cannot stop the SQL Server service, or many minidump files and many log files are generated in SQL Server 8. Data in a subscriber of a merge publication in SQL Server differs from the data in the publisher 8. The query performance may be slow when you query data from a view in SQL Server 8. Error message when you configure an immediate updating transactional replication in SQL Server You may receive an access violation error message when you import data by using the "Bulk Insert" command in SQL Server 8. A SQL Server session may be blocked for the whole time that a Snapshot Agent job runs 8. Error message when you try to run a query on a linked server in SQL Server 8. SQL Server may take a long time to complete the synchronization phase when you create a merge publication 8. Each query takes a long time to compile when you execute a single query or when you execute multiple concurrent queries in SQL Server 8. The query may return incorrect results, and the execution plan for the query may contain a "Table Spool" operator in SQL Server 8. A profiler trace in SQL Server may stop logging events unexpectedly, and you may receive the following error message: A memory leak occurs when you run a remote query by using a linked server in SQL Server 8. Error is logged in the SQL Server error log, and the instance of SQL Server temporarily stops responding 8. You receive an access violation error message when you try to perform a read of a large binary large object column in SQL Server 8. You may notice a decrease in performance when you run a query that uses the UNION ALL operator in SQL Server Service Pack 4 8. Error message when you run SQL Server You may experience heap corruption, and SQL Server may shut down with fatal access violations when you try to browse files in SQL Server Enterprise Manager on a Windows Server xbased computer 8. An access violation may occur when you run a query on a table that has a multicolumn index in SQL Server 8. The SQL Server process may end unexpectedly when you turn on trace flag -T and a profiler trace is capturing the Lock: DeadLock Chain event in SQL Server SP4 8. A deadlock occurs when the scheduled SQL Server Agent job that you add or that you update is running in SQL Server 8. The database status changes to Suspect when you perform a bulk copy in a transaction and then roll back the transaction in SQL Server 8. Error message when you try to apply a hotfix on a SQL Server based computer that is configured as a MSCS node: The password that you specify in a BACKUP statement appears in the SQL Server Errorlog file or in the Application event log if the BACKUP statement does not run in SQL Server 8. You may receive error messages when you use linked servers in SQL Server on a bit Itanium processor 8. Automatic checkpoints on some SQL Server databases do not run as expected 8. An error occurs when you try to access the Analysis Services performance monitor counter object after you apply Windows Server SP1 8. An error message is logged, and new diagnostics do not capture the thread stack when the SQL Server User Mode Scheduler UMS experiences a nonyielding thread in SQL Server Service Pack 4 8. You may experience concurrency issues when you run the DBCC INDEXDEFRAG statement in SQL Server 8. You receive an error message when you try to rebuild the master database after you have installed hotfix builds in SQL Server SP4 bit 8. You receive an "Error: Incorrect data is inserted unexpectedly when you perform a bulk copy operation by using the DB-Library API in SQL Server Service Pack 4 8. An access violation occurs in the Mssdi The results of the query may be returned much slower than you expect when you run a query that includes a GROUP BY statement in SQL Server 8. Some bit applications that use SQL-DMO and SQL-VDI APIs may stop working after you install SQL Server Service Pack 4 on an Itanium-based computer 8. You receive a "Getting registry information" message when you run the Sqldiag. You may experience slow server performance when you start a trace in an instance of SQL Server that runs on a computer that has more than four processors 8. A query that uses a view that contains a correlated subquery and an aggregate runs slowly 8. You receive query results that were not expected when you use both ANSI joins and non-ANSI joins 8. Description of the security update for Microsoft SQL Server Service Pack 4 GDR: Vulnerabilities in Microsoft SQL Server could allow remote code execution 8. Not all memory is available when AWE is enabled on a computer that is running a bit version of SQL Server SP4 8. Description of the security update for SQL Server Reporting Services Service Pack 2 8. Error message when you run a full-text query in SQL Server The "Audit Logout" event does not appear in the trace results file when you run a profiler trace against a linked server instance in SQL Server 8. You may intermittently experience an access violation error when a query is executed in a parallel plan and the execution plan contains either a HASH JOIN operation or a Sort operation in SQL Server 8. Error message when you run an UPDATE statement that uses two JOIN hints to update a table in SQL Server A error may occur you run a query that uses a hash join in SQL Server 8. You receive incorrect results when you run a query that uses a cross join operator in SQL Server SP3 8. Error message when you use SQL Server Server Network Utility may display incorrect protocol properties in SQL Server 8. The Subscriber may not be able to upload changes to the Publisher when you incrementally add an article to a publication in SQL Server SP3 8. You may receive a memory-related error message when you repeatedly create and destroy an out-of-process COM object within the same batch or stored procedure in SQL Server 8. The BULK INSERT statement silently skips insert attempts when the data value is NULL and the column is defined as NOT NULL for INT, SMALLINT, and BIGINT data types in SQL Server 8. You may receive error message , error message , and error message when many hashed buffers are available in SQL Server 8. You receive an error message when you try to delete records by running a Delete Transact-SQL statement in SQL Server 8. The query runs slower than you expected when you try to parse a query in SQL Server 8. Differential database backups may not contain database changes in the Page Free Space PFS pages in SQL Server 8. You may receive a error message when SQL Server performs a very large hash operation 8. Database recovery does not occur, or a user database is marked as suspect in SQL Server 8. SQL Server may stop responding to other requests when you perform a large deallocation operation 8. You receive a error message and SQL Server may stop responding to other requests when you perform large in-memory sort operations 8. Some complex queries are slower after you install SQL Server Service Pack 2 or SQL Server Service Pack 3 8. You experience non-convergence in a replication topology when you unpublish or drop columns from a dynamically filtered publication in SQL Server 8. You receive a "Server: The ERROR system function may return an incorrect value when you execute a Transact-SQL statement that uses a parallel execution plan in SQL Server bit or in SQL Server bit 8. You receive a error in SQL Server Service Pack 3 or in SQL Server Service Pack 3a when a worker thread becomes stuck in a registry call 8. Error message when you use a loopback linked server to run a distributed query in SQL Server Non-convergence may occur in a merge replication topology if the primary connection to the publisher is disconnected 8. You receive a "Msg " error message when you run an inner join query in SQL Server 8. Start times in the SQL Profiler are different for the Audit: Logout Events in SQL Server 8. A fetch on a dynamic cursor can cause unexpected results in SQL Server Service Pack 3 8. A SPID stops responding with a NETWORKIO 0x waittype in SQL Server Enterprise Manager when SQL Server tries to process a fragmented TDS network packet 8. An assertion error occurs when you insert data in the same row in a table by using multiple connections to an instance of SQL Server 8. A user-defined function returns results that are not correct for a query 8. An access violation exception may occur when multiple users try to perform data modification operations at the same time that fire triggers that reference a deleted or an inserted table in SQL Server on a computer that is running SMP 8. An Audit Object Permission event is not produced when you run a TRUNCATE TABLE statement 8. An access violation exception may occur when you run a query that uses index names in the WITH INDEX option to specify an index hint 8. The Log Reader Agent may cause error messages 8. Merge replication non-convergence occurs with SQL Server CE subscribers 8. Merge Agent may fail with an "Invalid character value for cast specification" error message 8. Shared page locks can be held until end of the transaction and can cause blocking or performance problems in SQL Server Service Pack 3 SP3 8. You may receive an error message when you try to run a complex query on an instance of SQL Server 8. SQL debugging does not work in Visual Studio. NET after you install Windows XP Service Pack 2 8. Additional diagnostics have been added to SQL Server to detect unreported read operation failures 8. SQL Server may underestimate the cardinality of a query expression under certain circumstances 8. You may notice incorrect values for the "Active Transactions" counter when you perform multiple transactions on an instance of SQL Server that is running on an SMP computer 8. You may receive a "The query processor could not produce a query plan" error message in SQL Server when you run a query that includes multiple subqueries that use self-joins 8. The MSSQLServer service exits unexpectedly in SQL Server Service Pack 3 8. The thread priority is raised for some threads in a parallel query 8. Profiler RPC events truncate parameters that have a text data type to 16 characters 8. An access violation exception may occur when you update a text column by using a stored procedure in SQL Server 8. You may receive an "Invalid object name When you use Transact-SQL cursor variables to perform operations that have large iterations, memory leaks may occur in SQL Server 8. Rows are not successfully inserted into a table when you use the BULK INSERT command to insert rows 8. SQL Server may not start if many users try to log in to SQL Server when SQL Server is trying to start 8. You receive a error message when you run an UPDATE statement and the isolation level is set to READ UNCOMMITTED 8. The Snapshot Agent may fail after you make schema changes to the underlying tables of a publication 8. You receive an error message when you try to restore a database backup that spans multiple devices 8. An access violation exception may occur when SQL Server runs many parallel query processing operations on a multiprocessor computer 8. The DBCC PSS Command may cause access violations and errors in SQL Server 8. You receive error message when you try to apply a transaction log to a server 8. Key Names Read from an. Ini File for a Dynamic Properties Task May Be Truncated 8. An invalid cursor state occurs after you apply Hotfix 8. An AWE system uses more memory for sorting or for hashing than a non-AWE system in SQL Server 8. Some queries that have a left outer join and an IS NULL filter run slower after you install SQL Server post-SP3 hotfix 8. SQL Query Analyzer may stop responding when you close a query window or open a file 8. The performance of a computer that is running SQL Server degrades when query execution plans against temporary tables remain in the procedure cache 8. Unconditional Update May Not Hold Key Locks on New Key Values 8. Access violation when you trace keyset-driven cursors by using SQL Profiler 8. An access violation occurs in SQL Server when a high volume of local shared memory connections occur after you install security update MS 8. An access violation occurs during compilation if the table contains statistics for a computed column 8. You cannot insert explicit values in an IDENTITY column of a SQL Server table by using the SQLBulkOperations function or the SQLSetPos ODBC function in SQL Server 8. Query performance may be slow and may be inconsistent when you run a query while another query that contains an IN operator with many values is compiled 8. A floating point exception occurs during the optimization of a query 8. Issues that are resolved in SQL Server build 8. Users Can Control the Compensating Change Process in Merge Replication 8. A query may fail with retail assertion when you use the NOLOCK hint or the READ UNCOMMITTED isolation level 8. An Internet Explorer script error occurs when you access metadata information by using DTS in SQL Server Enterprise Manager 8. Key Locks Are Held Until the End of the Statement for Rows That Do Not Pass Filter Criteria 8. An Access Violation Occurs When You Run DBCC UPDATEUSAGE on a Database That Has Many Objects 8. You may receive an "Internal SQL Server error" error message when you run a Transact-SQL SELECT statement on a view that has many subqueries in SQL Server 8. Slow Execution Times May Occur When You Run DML Statements Against Tables That Have Cascading Referential Integrity 8. A Deadlock Occurs If You Run an Explicit UPDATE STATISTICS Command 8. Linked Server Query May Return NULL If It Is Performed Through a Keyset Cursor 8. You receive an error message in SQL Server when you try to run a query that has multiple correlated subqueries 8. A Query with a LIKE Comparison Results in a Non-Optimal Query Plan When You Use a Hungarian SQL Server Collation 8. No Exclusive Locks May Be Taken If the DisAllowsPageLocks Value Is Set to True 8. SQL Server protocol encryption applies to JDBC clients 8. Rows are unexpectedly deleted when you run a distributed query to delete or to update a linked server table 8. You receive an error message when you run a parallel query that uses an aggregation function or the GROUP BY clause 8. Extremely Large Number of User Tables on AWE System May Cause BPool:: Map Errors 8. An Access Violation May Occur When You Run a Query That Contains 32, or More OR Clauses 8. A Cursor with a Large Object Parameter May Cause an Access Violation on CStmtCond:: Delayed domain authentication may cause SQL Server to stop responding 8. Lock monitor exception in DeadlockMonitor:: A Parallel Query May Generate an Access Violation After You Install SQL Server SP3 8. MS DTC Transaction Commit Operation Blocks Itself 8. A query that contains a correlated subquery runs slowly 8. You are prompted for password confirmation after you change a standard SQL Server login 8. Security patch for SQL Server Service Pack 3 8. Localized versions of SQL Mail and the Web Assistant Wizard may not work as expected in SQL Server 64 bit 8. A Transact-SQL Statement That Is Embedded in the Database Name Runs with System Administrator Permissions 8. Security Patch for SQL Server bit 8. Intense SQL Server activity results in spinloop wait 8. Distribution Cleanup Agent Incorrectly Cleans Up Entries for Anonymous Subscribers 8. An access violation exception may occur when you insert a row in a table that is referenced by indexed views in SQL Server 8. Invalid TDS Sent to SQL Server Results in Access Violation 8. Error Message May Occur When You Run a Complex Query 8. Internal Query Processor Error When Microsoft SQL Server Tries to Compile a Plan for a Complex Query 8. SQL Server Enterprise Manager unexpectedly quits when you modify a DTS package 8. An Access Violation May Occur When You Run DBCC DBREINDEX on a Table That Has Hypothetical Indexes 8. Query on the sysmembers Virtual Table May Fail with a Stack Overflow 8. OLE DB conversion errors may occur after you select a literal string that represents datetime data as a column 8. Error is Raised When SQL Server Compiles a Complex Query 8. SQL Server might produce an incorrect cardinality estimate for outer joins 8. Performance of a query that is run from a client program on a SQL Server SP3 database is slow after you restart the instance of SQL Server 8. You receive an error message when you use the SQL-DMO BulkCopy object to import data into a SQL Server table 8. Error May Display Message Text That Is Not Correct 8. You cannot install SQL Server SP3 on the Korean version of SQL Server 8. SQL Server Uninstall Option Does Not Remove All Files 8. A Full-Text Population Fails After You Apply SQL Server Service Pack 3 8. A DTS package that uses global variables ignores an error message raised by RAISERROR 8. A DELETE statement with a JOIN might fail and you receive a error 8. Merge Agent Can Resend Changes for Filtered Publications 8. Reinitialized SQL Server CE 2. You May Experience Slow Performance When You Debug a SQL Server Service 8. DTS Designer may generate an access violation after you install SQL Server Service Pack 3 8. Merge publications cannot synchronize on SQL Server Service Pack 3 8. A Transact-SQL query that uses views may fail unexpectedly in SQL Server SP2 8. Intense SQL Server Activity Results in Spinloop Wait in SQL Server Service Pack 2 8. Many Extent Lock Time-outs May Occur During Extent Allocation 8. A Large Number of NULL Values in Join Columns Result in Slow Query Performance 8. Merge Replication with Alternate Synchronization Partners May Not Succeed After You Change the Retention Period 8. A Query with an Aggregate Function May Fail with a Error 8. Distribution Agent Fails with "Violation of Primary Key Constraint" Error Message 8. A UNION ALL View May Not Use Index If Partitions Are Removed at Compile Time 8. Indexed View May Cause a Handled Access Violation in CIndex:: Update or Delete Statement Fails with Error During Row Lock Escalation 8. Unexpected results from partial aggregations based on conversions 8. Restoring a SQL Server 7. An error message occurs when you perform a database or a file SHRINK operation 8. Latch Time-Out Message Occurs When You Perform a Database or File SHRINK Operation 8. The JOIN queries in the triggers that involve the inserted table or the deleted table may return results that are not consistent 8. Cursors That Have a Long Lifetime May Cause Memory Fragmentation 8. Concurrency enhancements for the tempdb database 8. A DELETE Statement with a Self-Join May Fail and You Receive a Error 8. Merge Replication Reconciler Stack Overflow 8. A Memory Leak Occurs When Cursors Are Opened During a Connection 8. Parallel logical operation returns results that are not consistent 8. The SELECT Statement with Parallelism Enabled May Cause an Assertion 8. Replication Removed from Database After Restore WITH RECOVERY 8. Transaction Log Restore Fails with Message 8. Assertion and Error Message Occurs If You Try to Roll Back a Text Operation with READ UNCOMMITTED 8. A RESTORE DATABASE WITH RECOVERY Statement Can Fail with Error or Error 8. Lock escalation on a scan while an update query is running causes a error message to occur 8. SQL Server Grants Unnecessary Permissions or an Encryption Function Contains Unchecked Buffers 8. Slow Compile Time and Execution Time with Query That Contains Aggregates and Subqueries 8. SQL Extended Procedure Functions Contain Unchecked Buffers 8. Improved SQL Manager Robustness for Odd Length Buffer 8. Reorder outer joins with filter criteria before non-selective joins and outer joins 8. Unchecked Buffer May Occur When You Connect to Remote Data Source 8. SELECT with Timestamp Column That Uses FOR XML AUTO May Fail with Stack Overflow or AV 8. Handle Leak Occurs in SQL Server When Service or Application Repeatedly Connects and Disconnects with Shared Memory Network Library 8. Query That Uses DESC Index May Result in Access Violation 8. SELECT from Computed Column That References UDF Causes SQL Server to Terminate 8. Shared Table Lock Is Not Released After Lock Escalation 8. SELECT DISTINCT from Table with LEFT JOIN of View Causes Error Messages or Client Application May Stop Responding 8. SQLPutData May Result in Leak of Buffer Pool Memory 8. Querying Syslockinfo with Large Numbers of Locks May Cause Server to Stop Responding 8. SQLTrace Start and Stop is Now Reported in Windows NT Event Log for SQL Server 8. SQL Server Text Formatting Functions Contain Unchecked Buffers 8. Query Method Used to Access Data May Allow Rights that the Login Might Not Normally Have 8. Deletes, Updates and Rank Based Selects May Cause Deadlock of MSSEARCH 8. Error Using Two Indexes on a Column with Uppercase Preference Sort Order 8. Lock Monitor Uses Excessive CPU 8. Complex ANSI Join Query with Distributed Queries May Cause Handled Access Violation 8. Opening the Database Folder in SQL Server Enterprise Manager Takes a Long Time 8. Extreme Memory Usage When Adding Many Security Roles 8. Buffer Overflow Exploit Possible with Extended Stored Procedures 8. Exception Access Violation Encountered During Query Normalization 8. Scripting Object with Several Extended Properties May Cause Exception 8. CASE Using LIKE with Empty String Can Result in Access Violation or Abnormal Server Shutdown 8. Complex Distinct or Group By Query Can Return Unexpected Results with Parallel Execution Plan 8. Linked Server Query with Hyphen in LIKE Clause May Run Slowly 8. Sending Open Files as Attachment in SQL Mail Fails with Error 8. Optimizer Slow to Generate Query Plan for Complex Queries that have Many Joins and Semi-Joins 8. Microsoft SQL Server 7. Description of the security update for SQL Server 7. July 8, 7. An access violation exception may occur when you run a SELECT statement that contains complex JOIN operations in SQL Server 7. An attention signal that is sent from a SQL Server client application because of a query time-out may cause the SQL Server service to quit unexpectedly 7. Security patch for SQL Server 7. Cumulative security patch for SQL Server 7. Delayed domain authentication may cause SQL Server to stop responding 7. Replication Removed from Database After Restore WITH RECOVERY 7. Error message may occur when you restore a log that does not contain any transactions 7. Assertion and Error Message Occurs If You Try to Roll Back a Text Operation with READ UNCOMMITTED 7. SQL Server Text Formatting Functions Contain Unchecked Buffers 7. Query Method Used to Access Data May Allow Rights that the Login Might Not Normally Have 7. Update With Self Join May Update Incorrect Number Of Rows 7. SQL Server Profiler and SQL Server Agent Alerts May Fail to Work After Installing SQL Server 7. SQL Server May Generate Nested Query For Linked Server When Option Is Disabled 7. Incorrect Results with Join of Column Converted to Binary 7. Buffer Overflow Exploit Possible with Extended Stored Procedures 7. SQL RPC That Raises Error Will Mask ERROR with Msg 7. Data Modification Query with a Distinct Subquery on a View May Cause Error 7. Replication Initialize Method Causes Handle Leak on Failure 7. Linked Index Server Query Through OLE DB Provider with OR Clause Reports Error 7. Transactional Publications with a Filter on Numeric Columns Fail to Replicate Data 7. Temporary Stored Procedures in SA Owned Databases May Bypass Permission Checks When You Run Stored Procedures 7. Non-Admin User That Executes Batch While Server Shuts Down May Encounter Retail Assertion 7. Slow Compile Time on Complex Joins with Unfiltered Table 7. SQL Server Components that Access the Registry in a Cluster Environment May Cause a Memory Leak 7. Problems Mapping Characters to DB2 OLEDB Subscribers 7. Query with Complex View Hierarchy May Be Slow to Compile 7. Access Violation Under High Cursor Stress 7. Unable to Perform Automated Installation of SQL 7. SQL Cluster Install Fails When SVS Name Contains Special Characters 7. Integrated Security Sprocs Have Race Condition Between Threads That Can Result in an Access Violation 6. SQL Performance Counters May Cause Handle Leak in WinLogon Process 6. Terminating Clients with TSQL KILL May Cause ODS AV 6. ODS Errors During Attention Signal May Cause SQL Server to Stop Responding 6. SNMP Extended Stored Procedures May Leak Memory 6. Large Query Text from Socket Client May Cause Open Data Services Access Violation 6. Информационная безопасность 2,4k авторов , 6,4k публикаций. Open source 1k авторов , 2,3k публикаций. Высокая производительность авторов , 1,2k публикаций. Программирование 2,9k авторов , 6,5k публикаций. Разработка систем передачи данных 62 автора , публикаций. Разработка под Linux автор , публикация. Алгоритмы 1,3k авторов , 2,3k публикаций. Системное программирование авторов , публикации. Тестирование веб-сервисов автор , публикаций. Анализ и проектирование систем авторов , публикации. Добавить в закладки Константин Таранов kast карма. Спасибо за проделанную Вами работу. Но все же скажите зачем было дублировать информацию из Microsoft SQL Server Version List? Это не полное дублирование информации, я решил сделать свою версию, которая является компиляцией всех приведенных в начале статьи основных источников. В начале я как раз наткнулся на Microsoft SQL Server Version List и взял его за основу он обновлялся не слишком оперативно и имел ряд неточностей на тот момент. Затем я нашел подробнейшую и просто исчерпывающую KB, которая просто обязательна к прочтению. После Brent Ozar прислал новость о запуске sqlserverupdates. В итоге я на постоянной основе на github стараюсь оперативно обновлять данную информацию в том формате, который удобен для меня. Также я добавил некоторую информацию, которые не приведены на исходных ресурсах прямые ссылки для загрузок, sha1 хэши и прочее. Честно говоря, был еще один вопрос. А будет ли поддерживаться информация о билдах в этой статье. На мой вопрос Вы ответили. Ещё раз спасибо за полезный материал. Объемный труд, спасибо, поместил в закладки. Да, конечно, занимаюсь этим на постоянной основе, в начале статьи есть ссылка на github где стараюсь максимально оперативно добавлять выход новых версий. Выше была ссылка на sqlserverbuilds. У меня программа-установщик сама скачивает Express редакцию и сама же пишет, что скачанный файл повреждён. Сделал много попыток, результат неизменный. Самому этот файл не знаю как скачать, трафик не снифил. Обошёл проблему путём скачивания ISO редакции Developer. Погуглил — эта проблема регулярно возникает с года этак Я обошёл проблему, тратить на неё время больше не хочу. Установщик выглядел примерно так. Метки лучше разделять запятой. Сейчас Вчера Неделя Новые возможности C , которые можно ожидать в ближайшее время 19,4k Интересные публикации Хабрахабр Geektimes. Хорошее начало — половина дела GT. Запуск Java классов и JAR-ов не по учебнику. Анализируя Ethereum, Биткоин и более других криптовалют с помощью PostgreSQL GT. Критическая уязвимость механизма аутентификации BIND позволяет похищать и изменять DNS-записи серверов. Разделы Публикации Хабы Компании Пользователи Песочница. Информация О сайте Правила Помощь Соглашение Конфиденциальность. Услуги Реклама Тарифы Контент Семинары. Install SP1 then SP1 CU1 KB Install SP2 Or Developer Free then KB Install Or Developer Free then SP3 then KB Install R2 then SP3 R2 then SU KB Install then SP4 then SU KB Install SP4 then CU3 KB SQL Server SP1. SQL Server SP1 KB SQL Server SP2. SQL Server SP2 KB SQL Server SP3. SQL Server R2. SQL Server R2 SP3. SQL Server R2 SU. SQL Server SP4. SQL Server SU. Microsoft SQL Server vNext Community Technology Preview 1. Description of the security update for SQL Server CU. Description of the security update for SQL Server GDR. Microsoft SQL Server RTM. Deadlock cannot be resolved automatically when you run a SELECT query that can result in a parallel batch-mode scan. AlwaysOn availability groups are reported as NOT SYNCHRONIZING. Description of the security update for SQL Server QFE. Performance decrease when application with connection pooling frequently connects or disconnects in SQL Server. Data loss in clustered index occurs when you run online build index in SQL Server Hotfix for SQL SP2. SQL Server Service Pack 2 SP2. Description of the security update for SQL Server Service Pack 1 QFE. Data loss in clustered index occurs when you run online build index in SQL Server Hotfix for SQL SP1. Component installation process fails after you install SQL Server SP1. Description of the security update for SQL Server Service Pack 1 GDR. SQL Server Service Pack 1 SP1. Microsoft SQL Server With Power View For Multidimensional Models Customer Technology Preview CTP3. Microsoft Security Bulletin MS SQL Server R2 Service Pack 3 SP3. Description of the security update for SQL Server R2 Service Pack 2 QFE. Description of the security update for SQL Server R2 Service Pack 2 GDR. SQL Server R2 Service Pack 2 SP2. Access violation when you run DML statements against a table that has partitioned indexes in SQL Server R2. Slow performance when an AFTER trigger runs on a partitioned table in SQL Server R2. SQL Server R2 Service Pack 1 SP1. Database data files might be incorrectly marked as sparse in SQL Server R2 or in SQL Server even when the physical files are marked as not sparse in the file system. Non-yielding scheduler error when you run a query that uses a TVP in SQL Server or in SQL Server R2 if SQL Profiler or SQL Server Extended Events is used. Description of the security update for SQL Server SP3 QFE. Description of the security update for SQL Server SP3 GDR. SQL Server Service Pack 3 SP3. The Reporting Services service stops unexpectedly after you apply SQL Server SP1 CU 7 or CU8. Error message in SQL Server when you run an INSERT SELECT statement on a table. SQL Server RTM. Description of the security update for SQL Server Service Pack 4 QFE. SQL Server Agent job randomly stops when you schedule the job to run past midnight on specific days in SQL Server , in SQL Server or in SQL Server R2. Error when you use the ONLINE option to rebuild an index in SQL Server The query processor could not produce a query plan". The performance of database mirroring decreases when you run a database maintenance job that generates a large number of transaction log activities in SQL Server Error message when you run a distributed query in SQL Server In SQL Server , the session that runs the TRUNCATE TABLE statement may stop responding, and you cannot end the session. An ongoing MS DTC transaction is orphaned in SQL Server All the MDX queries that are running on an instance of SQL Server Analysis Services are canceled when you start or stop a SQL Server Profiler trace for the instance. The Replication Log Reader Agent may fail intermittently when a transactional replication synchronizes data in SQL Server An access violation occurs when you update a table through a view by using a cursor in SQL Server A stored procedure cannot finish its execution in SQL Server The change may be undone during the later synchronizations when you change an article on the subscriber in SQL Server A query takes longer to finish in SQL Server than in SQL Server when you open a fast forward-only cursor for the query. You cannot cancel the query execution immediately if you open a fast forward-only cursor for the query in SQL Server A federated database server stops responding when you run parallel queries on a multiprocessor computer that uses NUMA architecture in SQL Server Conflicts are not logged when you use the Microsoft SQL Server Subscriber Always Wins Conflict Resolver for an article in a merge replication in Microsoft SQL Server Some changes from subscribers who use SQL Server Compact Edition or Web synchronization are not uploaded to the publisher when you use the republishing model in a merge publication in Microsoft SQL Server The performance of a query that performs an insert operation or an update operation is much slower in SQL Server SP2 than in earlier versions of SQL Server You receive error when you run a complex query in SQL Server A SQL Server Agent job fails when you run the SQL Server Agent job in the context of a proxy account in SQL Server The Distribution Agent may skip some rows when you configure a transactional replication that uses the "-SkipErrors" parameter in SQL Server You may receive error messages when you try to log in to an instance of SQL Server and SQL Server handles many concurrent connections. You may receive more than , page faults when you try to back up a SQL Server database that contains hundreds of files and file groups. SQL Server system performance may be slow when you use a keyset-driven cursor to execute a FETCH statement. DeriveParameters method returns an exception when the input parameter is a XML parameter that has an associated XSD from an SQL schema. The monitor server does not monitor all primary servers and secondary servers when you configure log shipping in SQL Server When you run the "dbcc dbreindex" command or the "alter index" command, some transactions are not replicated to the subscribers in a transactional replication in SQL Server Errors may be generated in the tempdb database when you create and then drop many temporary tables in SQL Server Indexes may grow very large when you insert a row into a table and then update the same row in SQL Server The internal deadlock monitor may not detect a deadlock between two or more sessions in SQL Server When you start a merge agent, synchronization between the subscriber and the publisher takes a long time to be completed in SQL Server You experience a slow uploading process if conflicts occur when many merge agents upload changes to the publishers at the same time in SQL Server The merge agent fails and a "permission denied" error message is logged when you synchronize a SQL Server based merge publication. The merge agent does not use a specified custom user update to handle conflicting UPDATE statements in SQL Server A SQL Server login may have more permissions when you log on to an instance of SQL Server An incorrect result may appear in the subscribing database when you set database mirroring for a database and database failover occurs in SQL Server The replication on the server does not work any longer when you manually fail over databases in SQL Server You may receive an access violation error message when you run a SELECT query in SQL Server You cannot restore the log backups on the mirror server after you remove database mirroring for the mirror database in SQL Server A script task or a script component may not run correctly when you run an SSIS package in SQL Server build An access violation occurs when you run a DELETE statement or an UPDATE statement in the Itanium-based versions of SQL Server after you install security update MS Description of the security update for SQL Server QFE and MSDE July 8, The SPACE function always returns one space in SQL Server if the SPACE function uses a collation that differs from the collation of the current database. The data on the publisher does not match the data on the subscriber when you synchronize a SQL Server Mobile Edition subscriber with a SQL Server "merge replication" publisher. The CPU utilization may suddenly increase to percent when there are many connections to an instance of SQL Server on a computer that has multiple processors. An access violation may occur when you try to log in to an instance of SQL Server The foreign key that you created between two tables does not work after you run the CREATE INDEX statement in SQL Server You may receive an assertion or database corruption may occur when you use the bcp utility or the "Bulk Insert" Transact-SQL command to import data in SQL Server A hotfix for Microsoft SQL Server Service Pack 4 may not update all the necessary files on an xbased computer. In SQL Server , the synchronization process is slow, and the CPU usage is high on the computer that is configured as the Distributor. The merge agent fails intermittently when you use merge replication that uses a custom resolver after you install SQL Server Service Pack 4. CPU utilization may approach percent on a computer that is running SQL Server after you run the BACKUP DATABASE statement or the BACKUP LOG statement. SQL Server stops responding when you cancel a query or when a query time-out occurs, and error messages are logged in the SQL Server error log file. You may experience one or more symptoms when you run a "CREATE INDEX" statement on an instance of SQL Server You may receive inconsistent comparison results when you compare strings by using a width sensitive collation in SQL Server The server stops responding, the performance is slow, and a time-out occurs in SQL Server The result may be sorted in the wrong order when you run a query that uses the ORDER BY clause to sort a column in a table in SQL Server You cannot stop the SQL Server service, or many minidump files and many log files are generated in SQL Server Data in a subscriber of a merge publication in SQL Server differs from the data in the publisher. The query performance may be slow when you query data from a view in SQL Server You may receive an access violation error message when you import data by using the "Bulk Insert" command in SQL Server A SQL Server session may be blocked for the whole time that a Snapshot Agent job runs. Error message when you try to run a query on a linked server in SQL Server SQL Server may take a long time to complete the synchronization phase when you create a merge publication. Each query takes a long time to compile when you execute a single query or when you execute multiple concurrent queries in SQL Server The query may return incorrect results, and the execution plan for the query may contain a "Table Spool" operator in SQL Server A memory leak occurs when you run a remote query by using a linked server in SQL Server Error is logged in the SQL Server error log, and the instance of SQL Server temporarily stops responding. You receive an access violation error message when you try to perform a read of a large binary large object column in SQL Server You may notice a decrease in performance when you run a query that uses the UNION ALL operator in SQL Server Service Pack 4. You may experience heap corruption, and SQL Server may shut down with fatal access violations when you try to browse files in SQL Server Enterprise Manager on a Windows Server xbased computer. An access violation may occur when you run a query on a table that has a multicolumn index in SQL Server DeadLock Chain event in SQL Server SP4. A deadlock occurs when the scheduled SQL Server Agent job that you add or that you update is running in SQL Server The database status changes to Suspect when you perform a bulk copy in a transaction and then roll back the transaction in SQL Server The password that you specify in a BACKUP statement appears in the SQL Server Errorlog file or in the Application event log if the BACKUP statement does not run in SQL Server You may receive error messages when you use linked servers in SQL Server on a bit Itanium processor. Automatic checkpoints on some SQL Server databases do not run as expected. An error occurs when you try to access the Analysis Services performance monitor counter object after you apply Windows Server SP1. An error message is logged, and new diagnostics do not capture the thread stack when the SQL Server User Mode Scheduler UMS experiences a nonyielding thread in SQL Server Service Pack 4. You may experience concurrency issues when you run the DBCC INDEXDEFRAG statement in SQL Server You receive an error message when you try to rebuild the master database after you have installed hotfix builds in SQL Server SP4 bit. Incorrect data is inserted unexpectedly when you perform a bulk copy operation by using the DB-Library API in SQL Server Service Pack 4. The results of the query may be returned much slower than you expect when you run a query that includes a GROUP BY statement in SQL Server Some bit applications that use SQL-DMO and SQL-VDI APIs may stop working after you install SQL Server Service Pack 4 on an Itanium-based computer. You may experience slow server performance when you start a trace in an instance of SQL Server that runs on a computer that has more than four processors. A query that uses a view that contains a correlated subquery and an aggregate runs slowly. You receive query results that were not expected when you use both ANSI joins and non-ANSI joins. Vulnerabilities in Microsoft SQL Server could allow remote code execution. Not all memory is available when AWE is enabled on a computer that is running a bit version of SQL Server SP4. SQL Server Service Pack 4 SP4. Description of the security update for SQL Server Reporting Services Service Pack 2. The "Audit Logout" event does not appear in the trace results file when you run a profiler trace against a linked server instance in SQL Server You may intermittently experience an access violation error when a query is executed in a parallel plan and the execution plan contains either a HASH JOIN operation or a Sort operation in SQL Server A error may occur you run a query that uses a hash join in SQL Server You receive incorrect results when you run a query that uses a cross join operator in SQL Server SP3. Server Network Utility may display incorrect protocol properties in SQL Server The Subscriber may not be able to upload changes to the Publisher when you incrementally add an article to a publication in SQL Server SP3. You may receive a memory-related error message when you repeatedly create and destroy an out-of-process COM object within the same batch or stored procedure in SQL Server The BULK INSERT statement silently skips insert attempts when the data value is NULL and the column is defined as NOT NULL for INT, SMALLINT, and BIGINT data types in SQL Server You may receive error message , error message , and error message when many hashed buffers are available in SQL Server You receive an error message when you try to delete records by running a Delete Transact-SQL statement in SQL Server The query runs slower than you expected when you try to parse a query in SQL Server Differential database backups may not contain database changes in the Page Free Space PFS pages in SQL Server You may receive a error message when SQL Server performs a very large hash operation. Database recovery does not occur, or a user database is marked as suspect in SQL Server SQL Server may stop responding to other requests when you perform a large deallocation operation. You receive a error message and SQL Server may stop responding to other requests when you perform large in-memory sort operations. Some complex queries are slower after you install SQL Server Service Pack 2 or SQL Server Service Pack 3. You experience non-convergence in a replication topology when you unpublish or drop columns from a dynamically filtered publication in SQL Server The ERROR system function may return an incorrect value when you execute a Transact-SQL statement that uses a parallel execution plan in SQL Server bit or in SQL Server bit. You receive a error in SQL Server Service Pack 3 or in SQL Server Service Pack 3a when a worker thread becomes stuck in a registry call. Non-convergence may occur in a merge replication topology if the primary connection to the publisher is disconnected. You receive a "Msg " error message when you run an inner join query in SQL Server Logout Events in SQL Server A fetch on a dynamic cursor can cause unexpected results in SQL Server Service Pack 3. A SPID stops responding with a NETWORKIO 0x waittype in SQL Server Enterprise Manager when SQL Server tries to process a fragmented TDS network packet. An assertion error occurs when you insert data in the same row in a table by using multiple connections to an instance of SQL Server. A user-defined function returns results that are not correct for a query. An access violation exception may occur when multiple users try to perform data modification operations at the same time that fire triggers that reference a deleted or an inserted table in SQL Server on a computer that is running SMP. An Audit Object Permission event is not produced when you run a TRUNCATE TABLE statement. An access violation exception may occur when you run a query that uses index names in the WITH INDEX option to specify an index hint. The Log Reader Agent may cause error messages. Merge replication non-convergence occurs with SQL Server CE subscribers. Merge Agent may fail with an "Invalid character value for cast specification" error message. Shared page locks can be held until end of the transaction and can cause blocking or performance problems in SQL Server Service Pack 3 SP3. You may receive an error message when you try to run a complex query on an instance of SQL Server. NET after you install Windows XP Service Pack 2. Additional diagnostics have been added to SQL Server to detect unreported read operation failures. SQL Server may underestimate the cardinality of a query expression under certain circumstances. You may notice incorrect values for the "Active Transactions" counter when you perform multiple transactions on an instance of SQL Server that is running on an SMP computer. You may receive a "The query processor could not produce a query plan" error message in SQL Server when you run a query that includes multiple subqueries that use self-joins. The MSSQLServer service exits unexpectedly in SQL Server Service Pack 3. The thread priority is raised for some threads in a parallel query. Profiler RPC events truncate parameters that have a text data type to 16 characters. An access violation exception may occur when you update a text column by using a stored procedure in SQL Server When you use Transact-SQL cursor variables to perform operations that have large iterations, memory leaks may occur in SQL Server Rows are not successfully inserted into a table when you use the BULK INSERT command to insert rows. SQL Server may not start if many users try to log in to SQL Server when SQL Server is trying to start. You receive a error message when you run an UPDATE statement and the isolation level is set to READ UNCOMMITTED. The Snapshot Agent may fail after you make schema changes to the underlying tables of a publication. You receive an error message when you try to restore a database backup that spans multiple devices. An access violation exception may occur when SQL Server runs many parallel query processing operations on a multiprocessor computer. The DBCC PSS Command may cause access violations and errors in SQL Server You receive error message when you try to apply a transaction log to a server. Ini File for a Dynamic Properties Task May Be Truncated. An AWE system uses more memory for sorting or for hashing than a non-AWE system in SQL Server Some queries that have a left outer join and an IS NULL filter run slower after you install SQL Server post-SP3 hotfix. SQL Query Analyzer may stop responding when you close a query window or open a file. The performance of a computer that is running SQL Server degrades when query execution plans against temporary tables remain in the procedure cache. Unconditional Update May Not Hold Key Locks on New Key Values. Access violation when you trace keyset-driven cursors by using SQL Profiler. An access violation occurs in SQL Server when a high volume of local shared memory connections occur after you install security update MS An access violation occurs during compilation if the table contains statistics for a computed column. You cannot insert explicit values in an IDENTITY column of a SQL Server table by using the SQLBulkOperations function or the SQLSetPos ODBC function in SQL Server Query performance may be slow and may be inconsistent when you run a query while another query that contains an IN operator with many values is compiled. A floating point exception occurs during the optimization of a query. Users Can Control the Compensating Change Process in Merge Replication. A query may fail with retail assertion when you use the NOLOCK hint or the READ UNCOMMITTED isolation level. An Internet Explorer script error occurs when you access metadata information by using DTS in SQL Server Enterprise Manager. Key Locks Are Held Until the End of the Statement for Rows That Do Not Pass Filter Criteria. An Access Violation Occurs When You Run DBCC UPDATEUSAGE on a Database That Has Many Objects. You may receive an "Internal SQL Server error" error message when you run a Transact-SQL SELECT statement on a view that has many subqueries in SQL Server Slow Execution Times May Occur When You Run DML Statements Against Tables That Have Cascading Referential Integrity. A Deadlock Occurs If You Run an Explicit UPDATE STATISTICS Command. Linked Server Query May Return NULL If It Is Performed Through a Keyset Cursor. You receive an error message in SQL Server when you try to run a query that has multiple correlated subqueries. A Query with a LIKE Comparison Results in a Non-Optimal Query Plan When You Use a Hungarian SQL Server Collation. No Exclusive Locks May Be Taken If the DisAllowsPageLocks Value Is Set to True. SQL Server protocol encryption applies to JDBC clients. Rows are unexpectedly deleted when you run a distributed query to delete or to update a linked server table. You receive an error message when you run a parallel query that uses an aggregation function or the GROUP BY clause. An Access Violation May Occur When You Run a Query That Contains 32, or More OR Clauses. Delayed domain authentication may cause SQL Server to stop responding. A Parallel Query May Generate an Access Violation After You Install SQL Server SP3. MS DTC Transaction Commit Operation Blocks Itself. A query that contains a correlated subquery runs slowly. You are prompted for password confirmation after you change a standard SQL Server login. Security patch for SQL Server Service Pack 3. Localized versions of SQL Mail and the Web Assistant Wizard may not work as expected in SQL Server 64 bit. A Transact-SQL Statement That Is Embedded in the Database Name Runs with System Administrator Permissions. Security Patch for SQL Server bit. Intense SQL Server activity results in spinloop wait. Distribution Cleanup Agent Incorrectly Cleans Up Entries for Anonymous Subscribers. An access violation exception may occur when you insert a row in a table that is referenced by indexed views in SQL Server Invalid TDS Sent to SQL Server Results in Access Violation. Error Message May Occur When You Run a Complex Query. Internal Query Processor Error When Microsoft SQL Server Tries to Compile a Plan for a Complex Query. SQL Server Enterprise Manager unexpectedly quits when you modify a DTS package. An Access Violation May Occur When You Run DBCC DBREINDEX on a Table That Has Hypothetical Indexes. Query on the sysmembers Virtual Table May Fail with a Stack Overflow. OLE DB conversion errors may occur after you select a literal string that represents datetime data as a column. Error is Raised When SQL Server Compiles a Complex Query. SQL Server might produce an incorrect cardinality estimate for outer joins. Performance of a query that is run from a client program on a SQL Server SP3 database is slow after you restart the instance of SQL Server. You receive an error message when you use the SQL-DMO BulkCopy object to import data into a SQL Server table. Error May Display Message Text That Is Not Correct. You cannot install SQL Server SP3 on the Korean version of SQL Server SQL Server Uninstall Option Does Not Remove All Files. A Full-Text Population Fails After You Apply SQL Server Service Pack 3. A DTS package that uses global variables ignores an error message raised by RAISERROR. A DELETE statement with a JOIN might fail and you receive a error. Merge Agent Can Resend Changes for Filtered Publications. You May Experience Slow Performance When You Debug a SQL Server Service. DTS Designer may generate an access violation after you install SQL Server Service Pack 3. Merge publications cannot synchronize on SQL Server Service Pack 3. A Transact-SQL query that uses views may fail unexpectedly in SQL Server SP2. Intense SQL Server Activity Results in Spinloop Wait in SQL Server Service Pack 2. Many Extent Lock Time-outs May Occur During Extent Allocation. A Large Number of NULL Values in Join Columns Result in Slow Query Performance. Merge Replication with Alternate Synchronization Partners May Not Succeed After You Change the Retention Period. A Query with an Aggregate Function May Fail with a Error. Distribution Agent Fails with "Violation of Primary Key Constraint" Error Message. A UNION ALL View May Not Use Index If Partitions Are Removed at Compile Time. Update or Delete Statement Fails with Error During Row Lock Escalation. Unexpected results from partial aggregations based on conversions. An error message occurs when you perform a database or a file SHRINK operation. Latch Time-Out Message Occurs When You Perform a Database or File SHRINK Operation. The JOIN queries in the triggers that involve the inserted table or the deleted table may return results that are not consistent. Cursors That Have a Long Lifetime May Cause Memory Fragmentation. Concurrency enhancements for the tempdb database. A DELETE Statement with a Self-Join May Fail and You Receive a Error. Merge Replication Reconciler Stack Overflow. A Memory Leak Occurs When Cursors Are Opened During a Connection. Parallel logical operation returns results that are not consistent. The SELECT Statement with Parallelism Enabled May Cause an Assertion. Replication Removed from Database After Restore WITH RECOVERY. Transaction Log Restore Fails with Message Assertion and Error Message Occurs If You Try to Roll Back a Text Operation with READ UNCOMMITTED. A RESTORE DATABASE WITH RECOVERY Statement Can Fail with Error or Error Lock escalation on a scan while an update query is running causes a error message to occur. SQL Server Grants Unnecessary Permissions or an Encryption Function Contains Unchecked Buffers. Slow Compile Time and Execution Time with Query That Contains Aggregates and Subqueries. SQL Extended Procedure Functions Contain Unchecked Buffers. Improved SQL Manager Robustness for Odd Length Buffer. Reorder outer joins with filter criteria before non-selective joins and outer joins. Unchecked Buffer May Occur When You Connect to Remote Data Source. SELECT with Timestamp Column That Uses FOR XML AUTO May Fail with Stack Overflow or AV. Handle Leak Occurs in SQL Server When Service or Application Repeatedly Connects and Disconnects with Shared Memory Network Library. Query That Uses DESC Index May Result in Access Violation. SELECT from Computed Column That References UDF Causes SQL Server to Terminate. Shared Table Lock Is Not Released After Lock Escalation.
В свое время из-за немного громоздкой политики по выпуску обновлений для Microsoft SQL Server путался какой же из дистриубтивов нужно установить и откуда его скачать. Углубившись в данную тематику, в интернете нашел замечательные систематизирующие ресурсы, которые отвечали на мои вопросы они приведены в начале статьи. Надеюсь собранная информация будет полезна не только мне. Github версия в формате markdown на английском языке: SHA1 хэш можно легко получить с помощью встроенной Windows утилиты certutil. Например, для одного файла:. Для отправки комментария вам необходимо авторизоваться. Главная GitHub Видео Скрипты Проверь себя Полезные ссылки Книги Мероприятия Услуги. Полный обзор версий и обновлений Опубликовано Разнообразие версий Microsoft SQL Server и какая из них последняя? KB Наименоваие схем обновления для Microsoft SQL Server: KB Cтандартная терминология, которая используется для описания обновлений ПО от Microsoft: KB SQL Server Updates от Brent Ozar с возможность подписки: Community Technology Preview beta release RC: Released To Manufacturing — это оригинальный релиз сборки версии продукта, то есть то, что вы получите на DVD или при загрузке файла ISO от MSDN. Cumulative Update -накопительный пакет обновлений, содержащий баг фиксы и улучшения SP: Servise PackA tested, cumulative set of all hotfixes, security updates, critical updates, and updates. Service packs may also contain additional fixes for problems that are found internally since the release of the product and a limited number of customer-requested design changes or features. General Distribution Release; GDR исправления не должны включать любые из CU обновлений. Единый пакет обновлений, который включает один или несколько файлов, которые используются для решения адресных проблем. Обычно процедура установки SQL Server выглядит следующим образом: Устанавливается нужная вам стабильная версия на текущий момент рекомендуемые это или Затем устанавливается последний из доступных сервис паков Устанавливается последний накопительный пакет обнволений для устранения различного рода багов В случае необходимости для устранения конкретных проблем устанавливается нужный Hotfix Какие самые последние обновления доступны для SQL Server? Version Latest Update Build Number Release Date Support Ends Other Updates Download RC2 SQL Updates Download SP1 then CU5 KB Например, для одного файла: Полный список обновлений Microsoft SQ Server SQL Server Management Studio SSMS. Полный список расширений Microsoft SQL Server. Полный список инструментов и утилит Тонкая настройка Microsoft SQL Server с помощью флагов трассировки. Запись опубликована в рубрике В помощь администратору с метками update , version. Добавьте в закладки постоянную ссылку. Добавить комментарий Отменить ответ Для отправки комментария вам необходимо авторизоваться. Авторизация Регистрация Войти RSS записей RSS комментариев WordPress. Download SP1 then CU5 KB Download then SP3 then CU2 KB Download R2 then SP3 R2 then SU KB SQL R2 Updates. Download then SP4 then SU KB Download SP4 then CU3 KB
Характеристики счетчиков газа
Как выбрать цвет штор на кухню
Произведение двух событий это
У бабушки опухла рука
Сложен ли французский язык