Activity overview
Latest activity by bobking
We never really got a resolution on this, and think we just have the trace flag set permanently on our dev box. / comments
We never really got a resolution on this, and think we just have the trace flag set permanently on our dev box.
This also occurs (quite painfully) if the drive hosting the delta files (the "actual" databases to SQL) fills due to explosive growth of a clone's individual deltas. You'll get identical error 21s from SQL server. Some areas that we've had to disable to make a smoother experience with fewer giant delta files: * Make sure no index maintenance runs on the clones. * Turn off ghost page cleanup (trace flag 661) if your clones grow quickly just after creation. At idle, with no connections, the clones should be very small, but if they grow right cloning, look in sp_who2 for "GHOST CLEANUP" running on your database (generally with a low SPID). * Don't add/remove fields to compressed indexes. This causes a reindex but due to the nature of SQL's compression, the bits on index are likely to change dramatically, shuffling around quite a bit of data. / comments
This also occurs (quite painfully) if the drive hosting the delta files (the "actual" databases to SQL) fills due to explosive growth of a clone's individual deltas. You'll get identical error 21s ...
We are plagued by a very similar issue with ghost page cleanup after cloning, and had to set the same trace flag on our dev SQL box. I'm nervous, though, because we don't do any modification of our image as David does. So how are we ending up with ghost pages left over from our production backups (we image from a .bkp file)? Ghost page cleanup appears to be running fine in production, but something fishy is going on. We've been using Clone since before Christmas and this seems to have started only recently (last six weeks or so?). We can't pin it to a Clone release, but I'm wondering if an SQL Server patch changed something? We're on SQL 2014 CU 11 for both prod and dev. / comments
We are plagued by a very similar issue with ghost page cleanup after cloning, and had to set the same trace flag on our dev SQL box. I'm nervous, though, because we don't do any modification of our...
Support for SQL Compact Edition?
Am I just missing this or is this a missing feature? Does SQL Prompt analyze Compact Edition 3.5 databases for autocomplete, etc.? We're using Visual Studio 2008. We've also upgraded one machine to...