Automatic deployment of SQL Server Express databases and Solutions

A program was developed over the past few days, VS 2005 SQL Server Express. After carefully reading the documentation, we found that SQL Server Express supports XCOPY deployment, that is, as long as the target computer has SQL Server Express, you only need to copy the database, and you can configure the AttachDBFileName parameter in the connection string in the same directory of the program. The database is automatically attached to SQL Server Express and automatically Deattch after running. I felt good. As a result, I encountered an error: "The database has been compressed and cannot be created. We need to decompress it ". Dizzy. When will it be compressed? Is it Shinrk? It took n hours to go to bed.
The next day, I tried again. I had no solutions for reading the materials, and I had no solutions for accessing the Internet. I was reluctant to give up. I accidentally found that the Attach database in the management interface was also this error, but the database in the original directory was okay. An error occurs when you copy the database to the program directory (on D: disk, SQL Server Express is installed on C: disk. That's not the case, right?
After moving the program directory to drive C, everything is normal and then completely dizzy. Is it necessary to automatically mount the database on drive C ???
In addition, if the database file is set to read-only, it can be attached to any disk, but it is only a read-only database.
Although the problem has been solved, but do not understand the principle, is it a Bug, or is it my system problem?
In fact, Sybase's SQL Anywhere is really good. The database management system is started only when the database is started. The system is running and the database management system is automatically stopped, if SQL Server Express also supports this function, I don't like running an SQL Server service when I don't need a database. Access does not support stored procedures. It is not easy for Microsoft to love you.
BLOG: ZhangJinglin