MDF type IS SQL Server OK, so you want to know about how attaching a . MDF file as a user instance behaves in SQL Server Express. I've never really used that feature myself, but from all I understand, the only difference is that SQL Server Express must attach the .
MDF file before first using it during a session So you will experience a certain delay when the first request comes in - how much that is really hard to quantify and depends on your hardware, mostly (disk speed, available RAM). It should definitely not be more than a few seconds Once attached, as far as I understand it, there's no difference between a SQL Server Express user instance database and a "proper" real-life SQL Server Express database. So I don't think this is a major issue in terms of performance.
. MDF type IS SQL Server........... OK, so you want to know about how attaching a . MDF file as a user instance behaves in SQL Server Express.
I've never really used that feature myself, but from all I understand, the only difference is that SQL Server Express must attach the . MDF file before first using it during a session. So you will experience a certain delay when the first request comes in - how much that is really hard to quantify and depends on your hardware, mostly (disk speed, available RAM).
It should definitely not be more than a few seconds. Once attached, as far as I understand it, there's no difference between a SQL Server Express user instance database and a "proper" real-life SQL Server Express database. So I don't think this is a major issue in terms of performance.
2 ...but don't let that stop you. – Eric Sep 7 '09 at 14:07 Yep but there is a difference between a "real" SQL Server and Sql Server User Instances (.mdf files). I'm interested in performance differences.
– Veres Zoltan Sep 7 '09 at 14:09 1 The attach operation also needs to start a 'child instance', and that is the real bummer. The 'parent' Express instance needs to copy a set of master/model/msdb files into the user profile, then launch a SQL server process under the user context, wait for it to start (create tempdb etc), and then communicate with it. Once started, the child instance lasts up to one hour after last access.Msdn.microsoft.Com/en-us/library/bb264564%28SQL.90%29.aspx.
After the child instance is running and is connected, it behaves juts like any other instance with express restrictions. – Remus Rusanu Sep 7 '09 at 17:13 1 @Remus: OK, so the startup delay might be more significant than I first imagined. But you agree - once the attach is done, the performance should be the same as if it's a stand-alone, full-fledged SQL Server (Express) database, right?
– marc_s Sep 7 '09 at 19:07.
Once attached, as far as I understand it, there's no difference between a SQL Server Express user instance database and a "proper" real-life SQL Server Express database. So I don't think this is a major issue in terms of performance.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.