Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

system databases moving Expand / Collapse
Author
Message
Posted Saturday, January 11, 2014 6:23 PM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Today @ 10:00 AM
Points: 601, Visits: 772
Hi,
whenever we are moving system databases from one drive to another, do we need to move the path physically? or it automatically moves.
I want to try the rebuild the sql server. So I want to corrupt the master database so, I deleted the master mdf file and restore it back but instead of database corruption it is giving the following error message. Please let me know how can I corrupt the master database and can practice the rebuild the server.
And one more thing when I try to use the repair option I couldn't able to get all the things back to normal. The database engine service, replication is not working but SSAS, SSRS things are showing successfully repaired.

2014-01-10 21:34:26.44 Server Error: 26055, Severity: 16, State: 1.
2014-01-10 21:34:26.44 Server The SQL Server failed to initialize VIA support library [QLVipl.dll]. This normally indicates the VIA support library does not exist or is corrupted. Please repair or disable the VIA network protocol. Error: 0x7e.
2014-01-10 21:34:26.44 Server Error: 17182, Severity: 16, State: 1.
2014-01-10 21:34:26.44 Server TDSSNIClient initialization failed with error 0x7e, status code 0x60. Reason: Unable to initialize the VIA listener. The specified module could not be found.

2014-01-10 21:34:26.44 Server Error: 17182, Severity: 16, State: 1.
2014-01-10 21:34:26.44 Server TDSSNIClient initialization failed with error 0x7e, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The specified module could not be found.

2014-01-10 21:34:26.44 Server Error: 17826, Severity: 18, State: 3.
2014-01-10 21:34:26.44 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-01-10 21:34:26.44 Server Error: 17120, Severity: 16, State: 1.
2014-01-10 21:34:26.44 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Post #1530073
Posted Sunday, January 12, 2014 4:10 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:51 AM
Points: 40,176, Visits: 36,575
When you move databases from one place to another (any database), you have to move the files, SQL doesn't automatically move files around for you.

Looks like you may want to reinstall. Repair wasn't the correct fix for a missing master database in the first place.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1530089
Posted Sunday, January 12, 2014 11:37 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Today @ 10:00 AM
Points: 601, Visits: 772
Thanks Gail. I restored the data file again but still it is showing me that error.
Post #1530136
Posted Sunday, January 12, 2014 12:12 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 7:13 PM
Points: 6,466, Visits: 13,919
To corrupt a user database or the master database check my article at this link

Are there any other errors from the windows app log?


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1530139
Posted Sunday, January 12, 2014 12:53 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:51 AM
Points: 40,176, Visits: 36,575
ramana3327 (1/12/2014)
Thanks Gail. I restored the data file again but still it is showing me that error.


I suggested reinstalling, not restoring a data file.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1530147
Posted Tuesday, January 14, 2014 5:25 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 4:30 AM
Points: 2,885, Visits: 3,253
IMHO moving a system database on a test server can be a useful part of educating yourself in how SQL Server works, what can break, and what needs to be done to fix it.

Moving a system database on a production server is not necessary, adds risk to your installation, and takes time away from doing productive tasks.

Just IMHO, not cast in stone...


Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2014, 2012, 2008 R2, 2008 and 2005. 18 October 2014: now over 31,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Concept: "Pizza Apartheid" - the discrimination that separates those who earn enough in one day to buy a pizza if they want one, from those who can not.
Post #1530627
Posted Tuesday, January 14, 2014 1:11 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, October 3, 2014 9:33 AM
Points: 72, Visits: 405
EdVassie (1/14/2014)
IMHO moving a system database on a test server can be a useful part of educating yourself in how SQL Server works, what can break, and what needs to be done to fix it.

Moving a system database on a production server is not necessary, adds risk to your installation, and takes time away from doing productive tasks.

Just IMHO, not cast in stone...


It isn't necessary until it is ;)

I've had to move tempdb due to space issues (for example, on a production server where the drive space for tempdb wasn't allocated large enough) and it's a good idea to at least know how to move them, just in case.

The instructions here work like a charm: [url=http://technet.microsoft.com/en-us/library/ms345408.aspx][/url]
Post #1530853
Posted Tuesday, January 14, 2014 1:28 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 8:51 AM
Points: 40,176, Visits: 36,575
Moving TempDB is easy. The other three, not so much.


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1530859
Posted Tuesday, January 14, 2014 1:52 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 7:13 PM
Points: 6,466, Visits: 13,919
On many occasions I've been asked by clients to reconfigure a sql server and move the system databases, mainly because a vendor has deployed a server with mal configured local storage and the client has preferred to move the sql server drives to consolidated storage. It's deeply involved and you have to know exactly what needs to be moved, its not just the system databases usually
I'll leave you to work out what else is required, if you get stuck shout.


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1530866
Posted Tuesday, January 14, 2014 1:54 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 7:13 PM
Points: 6,466, Visits: 13,919
GilaMonster (1/14/2014)
Moving TempDB is easy. The other three, not so much.

+1


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1530867
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse