SQL Server Attach Database

-
All,
Today morning I had an call from supplier that they need to get attached their files to the database . As SQL Server amazingly does this for us using SSMS , but i decided to give brain some food.

Here it goes syntaxtically . Open  SQL QUERY Session and apply the following as shown below .

CREATE DATABASE Transearch_KE  
    ON (FILENAME = 'D:\data\MSSQL14.KPHQTSRCH01SQP_1\MSSQL\Data\Transearch_KE.mdf'),  
    (FILENAME = 'L:\logs\MSSQL14.KPHQTSRCH01SQP_1\MSSQL\Log\Transearch_KE_log.ldf')  
    FOR ATTACH;


Messages
Converting database 'Transearch_KE' from version 852 to the current version 869.
Database 'Transearch_KE' running the upgrade step from version 852 to version 853.
Database 'Transearch_KE' running the upgrade step from version 853 to version 854.
Database 'Transearch_KE' running the upgrade step from version 854 to version 855.
Database 'Transearch_KE' running the upgrade step from version 855 to version 856.
Database 'Transearch_KE' running the upgrade step from version 856 to version 857.
Database 'Transearch_KE' running the upgrade step from version 857 to version 858.
Database 'Transearch_KE' running the upgrade step from version 858 to version 859.
Database 'Transearch_KE' running the upgrade step from version 859 to version 860.
Database 'Transearch_KE' running the upgrade step from version 860 to version 861.
Database 'Transearch_KE' running the upgrade step from version 861 to version 862.
Database 'Transearch_KE' running the upgrade step from version 862 to version 863.
Database 'Transearch_KE' running the upgrade step from version 863 to version 864.
Database 'Transearch_KE' running the upgrade step from version 864 to version 865.
Database 'Transearch_KE' running the upgrade step from version 865 to version 866.
Database 'Transearch_KE' running the upgrade step from version 866 to version 867.
Database 'Transearch_KE' running the upgrade step from version 867 to version 868.
Database 'Transearch_KE' running the upgrade step from version 868 to version 869.



Screenshot for your reference .

Comments

Post a Comment

Popular posts from this blog

SQL SERVER – Event ID 107- Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.

-
SQL SERVER – Event ID 107- Report Server Windows Service cannot connect to the report server database. Error with Report Server One of my clients reported an error which is the subject of the blog. In the event viewer they were seeing below error:     Event Type: Error Event Source: Report Server Windows Service (MSSQLSERVER) Event Category: Management Event ID: 107 Computer: SQLSERVER Description: Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database The error is generic because it doesn’t tell the exact error which is causing a connectivity error. My immediate question was that, are there any more errors? So, I asked them to look at Reporting Service Log file. Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database. The application domain WindowsService_17 failed to initialize. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report se
Read more

SQL Server Builds Information

-
Image
Very Useful information about SQL Server Builds .  It is nicely presented in the blog . Please see  below for our reference . Microsoft SQL Server Version List What version of SQL Server do I have? This unofficial build chart lists all of the known Service Packs ( SP ), Cumulative Updates ( CU ), patches, hotfixes and other builds of MS SQL Server 2017, 2016, 2014, 2012, 2008 R2, 2008, 2005, 2000, 7.0, 6.5 and 6.0 that have been released. Useful articles: How to identify your SQL Server version and edition SQL Server Internal Database Versions Microsoft SQL Server Support Lifecycle Microsoft SQL Server Home Microsoft SQL Server Developer Center Microsoft TechNet: Microsoft SQL Server Microsoft Knowledge Base Sqlservr.exe versions   Quick summary:   RTM (no SP ) SP1 SP2 SP3 SP4   SQL Server 2017      codename vNext 14.0.1000.169 *new           SQL Server 2016 13.0.1601.5 13.0.4001.0 or 13.1.4001.0 13.0.5026.0 or 13.2.5026.0   S
Read more

Using DBCA silent install and disabling automatic memory management

-
Image
Avoid issue [DBT-11211] /app/oracle/product/12.2.0/dbhome_1/bin=> dbca -silent -createDatabase -templateName db_kp_template.dbt -gdbname dgtest1 -sid dgtest1 -responseFile NO_VALUE -characterSet AL32UTF8 -memoryPercentage 20 -emConfiguration NONE [FATAL] [DBT-11211] The Automatic Memory Management option is not allowed when the total physical memory is greater than 4GB.    CAUSE: The current total physical memory is 11GB. Solution : disable automatic memory management with in the response file and you will be fine :) .  /app/oracle/product/12.2.0/dbhome_1/assistants/dbca/templates=> dbca -silent -createDatabase -templateName db_kp_template.dbt -gdbname dgtest1 -sid dgtest1 -responseFile NO_VALUE -characterSet AL32UTF8 -automaticMemoryManagement FALSE -memoryPercentage 20 -emConfiguration NONE Enter SYS user password: Enter SYSTEM user password: [WARNING] [DBT-06208] The 'SYS' password entered does not conform to the Oracle recommended standards.    CAUS
Read more