User profile for PDinCA

"Swap to same DB in next Server" is definitely the default behavior I'd want if you pursue this approach. The way that Multi-Script works would be good to port to Search... As in, let us define lists of Servers and Databases and let the dropdown allow us to select a list, then be able to check/uncheck each db in the list and hit the (not there yet) "Search Now" button. At the very least, if you could give us some options we can all be happy to one degree or another. (Wish SSMS behaved like the original poster suggested, instead of "master" just because that's my login default DB... Bites! Lost count of the number of times I've added a table to master - OOPS!) / comments

"Swap to same DB in next Server" is definitely the default behavior I'd want if you pursue this approach.The way that Multi-Script works would be good to port to Search... As in, let us define lis...

0 votes

Despite having stopped the SQB Core Service, it restarts itself and re-locks the data.sdf file... DISABLING Restart means that any scheduled SQL Backup Job will CRASH! SQL Backup failed with exit code: 5148 SQL error code: 0 [SQLSTATE 42000] (Error 50000). The step failed. Is there opportunity here for a more friendly message, as in "The SQL Backup Service is not running on the Server, backups cannot be performed."...? Anyway, the UI on the 64-bit cluster appears to be showing correct information now. HOWEVER, the UI on my Windows7 box just barfed (a.k.a., DIED), again, despite my having deleted all local cache files just after I deleted them from the cluster: SQLBackup Unable to open the database file unable to open database file WorkerExecutionException at RedGate.SQLBackup.Engine.ConfigurableThreadPool.a(Exception ) at RedGate.SQLBackup.Engine.ConfigurableThreadPool.a.b() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() ---------- SQLiteException Unable to open the database file unable to open database file at System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt) at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt) at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery() at g.g(Server ) at g.b(Object ) To be clear: 1. Followed each step of your "temporary" fix. 2. Step 3 was executed on the cluster, then on the W7 box. 3. The SQB Service was restarted. 4. The UI was started on the cluster, waited until activity occurred and verified the presentation was correct. 5. Closed all programs on the cluster for my session and logged off. 6. Opened the UI on my W7 box. 7. The "usual" red-X appeared on the cluster (the one I'd just successfully fixed). 8. The UI Exceptioned. / comments

Despite having stopped the SQB Core Service, it restarts itself and re-locks the data.sdf file... DISABLING Restart means that any scheduled SQL Backup Job will CRASH! SQL Backup failed with exit c...

0 votes

Location of the data.sdf file, please? Searched the Production cluster's c: drive and no file found... / comments

Location of the data.sdf file, please? Searched the Production cluster's c: drive and no file found...

0 votes

Slight problem... Step 2 of your "temporary" solution is being blocked... To temporarily alleviate the problem, you can purge the history by deleting the following (in order). This should not interfere with log shipping. 1) the contents of the five backup related tables and three restore related tables in MSDB 2) the data.sdf (whilst the SQB service is not running) 3) the local cache on any workstations with the UI installed I stopped the SQL Backup Agent and went to the C:\ProgramData\Red Gate\SQL Backup\Data\(LOCAL) folder to rename the data.sdf but was prevented. How does one free up the file as I'm stymied trying to access the Compact Edition in any way in an effort to, perhaps, run some DELETEs... Obvious lack of CE knowledge exhibited here :? / comments

Slight problem... Step 2 of your "temporary" solution is being blocked... To temporarily alleviate the problem, you can purge the history by deleting the following (in order). This should not int...

0 votes

As far as running SQL Backup UI on another box goes, I can run it on the 64-bit WS2008/SS2008 box. Everything appears INITIALLY normal and I'm not solicited to upgrade the cache each time, and the History is complete and correctly represented (color and height of lines). HOWEVER, on the first automatic Refresh, the history lines all go full-height and grey! I'll attempt to screen-capture and email to you... The Exception I copied re the failure to open the database file DOES result in a complete failure of the UI. Perhaps, rather than exception and die, the UI should "give an informational status area, perhaps in the UI's status area at the foot of the window, and retry the operation"??? To die like this is rather unfriendly in light of the problem being an "unexpected communication break" (to quote you), which we all experience from time to time... "Fix pending" perhaps? / comments

As far as running SQL Backup UI on another box goes, I can run it on the 64-bit WS2008/SS2008 box. Everything appears INITIALLY normal and I'm not solicited to upgrade the cache each time, and the...

0 votes

Screen-shot emailed. Grey-full-height occurs on first and subsequent refreshes of an expanded Server - ANY server. / comments

Screen-shot emailed. Grey-full-height occurs on first and subsequent refreshes of an expanded Server - ANY server.

0 votes

Thanks for the unexpectedly rapid response and warning about SS2008. If your tech squad would like to remote in, like last time, I'm happy to oblige... Enjoy the weekend. / comments

Thanks for the unexpectedly rapid response and warning about SS2008. If your tech squad would like to remote in, like last time, I'm happy to oblige... Enjoy the weekend.

0 votes

I tried to run the repair utility on my local machine as the readme.txt says the utility will attempt to repair the "local cache". Somewhat predictably, as SQL Backup SERVER Components are not ins...

0 votes

From a permissions perspective, I have full admin rights on this box. I also have "Effective Permissions" of "Full Control" all the way down the c:\...\AppData\ folder tree, including the localDataCache.dat file. I am concerned that SQL Backup should have issues every time I use it. I only have Microsoft's Security Essentials running, alongside Windows Defender. I do not have Symantec's products, like I had when this box was an XP Pro machine. I have excluded C:\Users\<<user>>\AppData\Local\Red Gate\ and the child \SQL Backup folder from monitoring by Essentials. These actions have had no effect at all. On firing up SQL Backup, again, I chose "Later" on the latest invoke of the UI and now have 1.dat, 2.dat, 3.dat and the localDataCache.dat files in the \Server Data folder. Within the UI: 1. Expanded the 64-bit Server node. It initially displayed the history in green with what appeared to be correct icon-heights (transaction log backup - short and green). NOTE: Correction - It appears that "History" presentation is "inconsistent", SQLB doesn't always "wipe server history". 2. The node automatically refreshed. Now the markers are full height, and grey, and each says I have 2 items that were successful against every database that should have activity. However, there were NOT 2 items, just ONE, and "grey" means "what?" 3. I closed the UI. 4. I opened the UI -IT EXCEPTIONED!!!: SQLBackup Unable to open the database file unable to open database file WorkerExecutionException at RedGate.SQLBackup.Engine.ConfigurableThreadPool.a(Exception ) at RedGate.SQLBackup.Engine.ConfigurableThreadPool.a.b() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() ---------- SQLiteException Unable to open the database file unable to open database file at System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt) at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt) at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery() at g.g(Server ) at g.b(Object ) THIS PRODUCT IS BROKEN! "Process Explorer" is a black box to me. What EXACTLY is one supposed to do to "...see if anything is happening to those files via Process Explorer's handle search or a similar tool."? Also, frequently, when I expand my Production Group, the 64-bit SQL Cluster shows a red-X, and I get: System.NullReferenceException: Object reference not set to an instance of an object. at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at RedGate.Shared.SQL.Server.SQLServer.GetDatabasesEx(Boolean forceRefresh) at RedGate.Shared.SQL.Server.SQLServer.GetDatabasesEx(String server, Boolean integratedSecurity, String username, String password, Boolean forceRefresh) at RedGate.SQLBackup.Engine.Server.a() at RedGate.SQLBackup.Engine.Server.RefreshDatabases() at RedGate.SQLBackup.Engine.Server.RefreshServerInformation() at RedGate.SQLBackup.Engine.Server.OpenConnection(Boolean updateData) It appears to clean itself up almost immediately, but surely this is not correct behavior... / comments

From a permissions perspective, I have full admin rights on this box. I also have "Effective Permissions" of "Full Control" all the way down the c:\...\AppData\ folder tree, including the localDat...

0 votes

Thanks, that cleared it up - only 33 patches to catch up on :lol: / comments

Thanks, that cleared it up - only 33 patches to catch up on :lol:

0 votes

How can we help you today?

PDinCA

Comments