The enterprise geodatabase can�??t be attached by sql server,

607
4
12-21-2012 08:33 AM
Highlighted
Honored Contributor
The enterprise geodatabase can�??t be attached by sql server,

I tried to attach my mdf database to the sql server but sounds not to work. I got the error in the screenshots below:

[ATTACH=CONFIG]20135[/ATTACH], [ATTACH=CONFIG]20136[/ATTACH]

What might be the problem?

Thank you

Best

Jamal
Reply
0 Kudos
4 Replies
Highlighted
Esri Esteemed Contributor
Hi Jamal,

Does the directory "C:\student\Class_data_files" exist on your database server?  If it doesn't, specify another location to store the .MDF in the Attach Databases dialog.
Reply
0 Kudos
Highlighted
by Anonymous User
Not applicable
Original User: Jamal432@gmail.com

Hi Jamal,

Does the directory "C:\student\Class_data_files" exist on your database server?  If it doesn't, specify another location to store the .MDF in the Attach Databases dialog.


Thank you Jake for the answer.

Sounds that I got a problem of versions as shown in the screenshot below:

[ATTACH=CONFIG]20142[/ATTACH]

�?� How to manage to downgrade the mdf file? How this is related to the sql server 2008? And in this sense what is the version of sql server 2008?
�?� Why switching the mdf file and its ldf file still introduces problem?

Best

Jamal
Reply
0 Kudos
Highlighted
Esri Esteemed Contributor
Database version 661 means that the database was from a SQL Server 2008  R2 instance, where version 655 means SQL Server 2008 instance. You'll  need to upgrade to the R2 version in order to attach the database.
Reply
0 Kudos
Highlighted
by Anonymous User
Not applicable
Original User: Jamal432@gmail.com

Database version 661 means that the database was from a SQL Server 2008  R2 instance, where version 655 means SQL Server 2008 instance. You'll  need to upgrade to the R2 version in order to attach the database.


Many thanks Jake for the prompt answer. This is very useful.

It try to sort out this issue based on your valuable advice.

Best

Jamal
Reply
0 Kudos