亚洲免费在线-亚洲免费在线播放-亚洲免费在线观看-亚洲免费在线观看视频-亚洲免费在线看-亚洲免费在线视频

數據庫分卷備份和還原

系統 1981 0

from: http://www.sql-server-performance.com/2011/restoring-sql-server-database-low-disk-space/

Performing a Database Restore is a part of a DBA’s daily life. A DBA may need to perform a Restore due to various reasons such as recovery, refreshing a database for testing purpose etc. Many times it can be difficult to perform a Restore due to corrupted media, low disk space on the server and so on. In this article, I will outline one approach which I used to Restore the backup of the Production Database a test environment.

Scenario

A couple of days back, members of my support team approached me saying that they are unable to refresh a database named ABC on the OLTP development environment with the copy of the backup of the same database from the Production server. The backup copy taken from the Production server was around 75 GB in size. On our dev machine we were had just 1 dedicated drive(D) for SQL Server which was having just 70 GB of free space left on it.

Restore Solution

After having a detailed look, I came to a conclusion that I could not free up any space on the D drive of the dev machine. One important point to mention is that our entire dev machines were in a different domain than the staging and production boxes.

I logged on to the Production Server and decided to split the backup of the database named ABC into two equal parts using the T-SQL as shown below:

                
                  BACKUP
                
                
                  DATABASE
                
                 ABC
                
TO DISK = ' B:\DB Backups\ABC_1.bak ' ,
DISK = ' B:\DB Backups\ABC_2.bak '
GO
              

Once the above block of T-SQL statement is executed, it splits the Full Backup of the database named ABC present on the Production server into two equal parts. For example, if the size of a database is 76 GB then it will be divided into two equal parts each of size 36 GB.

Once the full backup gets split into two equal parts, I can then perform the RAR on them. Obviously first performing the RAR and then moving them to the different server would be much faster than moving the original copy of a much bigger size. Once the split files were zipped successfully I then moved them onto my staging server. This is because the staging box was pretty good in terms of resources and also since both the Production and Staging servers were in different Data Centers, due to good hardware the copying process worked much faster. As discussed earlier the free space available on the dev OLTP box was just 70 GB whereas the backup copy was 75 GB therefore it was not possible to transfer the zipped copies of the full backup to the dev OLTP box. I was having another box which was used as a SSIS Dev server with large amounts of free space. They are as follows:

Drive D had 49.9 GB free space

Drive C had 55 GB free space

The dev machines were standalone machines and not a cluster, therefore there were no issues for in copying 1 zipped file of the backup onto the C drive.

I then moved one copy of the zipped file onto the folder named? backups ?which was on the C drive of the dev SSIS server and the other zipped file onto the folder named? Backup_03102011_DB? present on the D drive. I gave Full permissions on both these folders.

I then unzipped the two backup files on the dev SSIS server. Once done, I then logged on to the Dev OLTP machine and against the database named ABC I executed the following T-SQL statement to restore the database.

                          
                            RESTORE
                          
                          
                            DATABASE
                          
                           ABC
                          
FROM DISK = ' \\10.A.A.A\backups\ABC_1.bak ' ,
DISK = ' \\10.A.A.A\Backup_03102011_DB\ABC_2.bak '
WITH MOVE ' ABC_Data ' TO ' D:\Program Files\Microsoft SQLServer\MSSQL.1\MSSQL\Data\ABC_Data_1.mdf ' ,
MOVE ' ABC_Log ' TO ' D:\Program Files\Microsoft SQLServer\MSSQL.1\MSSQL\Data\ABC_Log.ldf '
GO
                        

Where 10.A.A.A is the IP Address of the dev machine.

Once the above block of T-SQL code was executed successfully, I then changed the owner of the database to sa by executing the following query against the database named ABC.

                          
                            Exec
                          
                           sp_changedbowner ‘sa’
                        
                        

The next step involved mapping the Orphaned users. In order to find the Orphaned users, you need to execute the below T-SQL query against the ABC database on dev OLTP machine

                          sp_change_users_login 
                          
                            @Action
                          
                          
                            =
                          
                          
                            '
                          
                          
                            Report
                          
                          
                            '
                          
                        


Once the above query is executed, it will list all the Orphaned users present in the database named ABC. In order to fix this you will need to execute the below T-SQL query:

                          
                            exec
                          
                           sp_change_users_login 
                          
                            @Action
                          
                          
                            =
                          
                          
                            '
                          
                          
                            update_one
                          
                          
                            '
                          
                          , 
                          
                            @UserNamePattern
                          
                          
                            =
                          
                          
                            '
                          
                          
                            User Name
                          
                          
                            '
                          
                          , 
                          
                            @LoginName
                          
                          
                            =
                          
                          
                            '
                          
                          
                            Login Name
                          
                          
                            '
                          
                          ;
                        


I hope you all have enjoyed reading this article. Any suggestions or comments on this process would be most welcome.

數據庫分卷備份和還原


更多文章、技術交流、商務合作、聯系博主

微信掃碼或搜索:z360901061

微信掃一掃加我為好友

QQ號聯系: 360901061

您的支持是博主寫作最大的動力,如果您喜歡我的文章,感覺我的文章對您有幫助,請用微信掃描下面二維碼支持博主2元、5元、10元、20元等您想捐的金額吧,狠狠點擊下面給點支持吧,站長非常感激您!手機微信長按不能支付解決辦法:請將微信支付二維碼保存到相冊,切換到微信,然后點擊微信右上角掃一掃功能,選擇支付二維碼完成支付。

【本文對您有幫助就好】

您的支持是博主寫作最大的動力,如果您喜歡我的文章,感覺我的文章對您有幫助,請用微信掃描上面二維碼支持博主2元、5元、10元、自定義金額等您想捐的金額吧,站長會非常 感謝您的哦!!!

發表我的評論
最新評論 總共0條評論
主站蜘蛛池模板: 精品偷拍模特露出丝袜在线 | 成人欧美视频在线看免费 | 私人影院在线免费观看 | 手机在线中文字幕 | 天天干天天骑 | 久久国产免费福利资源网站 | 美女被爆羞羞视频网站视频 | 日日摸日日添日日透 | 亚洲福利精品一区二区三区 | 在线观看日本免费视频大片一区 | 国产亚洲视频在线观看 | 婷婷婷色 | 欧美男女性生活视频 | 亚洲伊人久久大香线蕉啊 | 欧美一级免费大片 | 97视频在线观看免费视频 | 最新四虎4hu影库地址在线 | 国产资源福利 | 精品久久天干天天天按摩 | 中国xxx69免费| 精品国产_亚洲人成在线高清 | 欧美一级在线观看 | 成 人 a v免费视频 | 最近手机中文字幕1页 | 免费看一级大片 | 伊人久久国产免费观看视频 | 色伊伊| 91久久国产青草亚洲 | 亚洲精品国产自在久久出水 | 青青久久精品国产免费看 | 可以看美女隐私的网站 | 国产成人午夜片在线观看 | 四虎影视永久地址 | 在线综合视频 | 抱着cao才爽免费观看 | 久久久久久a亚洲欧洲aⅴ | 中文字幕久久亚洲一区 | 日本在线高清不卡 | 久草综合视频在线 | 欧美日韩在线视频 | 久久99精品久久久久久国产人妖 |