Activity overview
Latest activity by wayneph
Scripting of Object Level Recovery?
I have a few PeopleSoft databases that each contain 20,000+ tables in them. Occasionally we do something in a development environment where we want to restore tables from the last back up. With t...
Chris,
Sorry for the delayed response. It's been a busy couple of weeks and there isn't a slowdown in sight... That being said, here is the information you requested from our Production Database:
Columns: 658508
Objects: 51084
One of our servers has multiple Training and Test databases that each have the numbers above. We are getting ready to start a PeopleSoft Financials implementation (these databases are PeopleSoft HCM) and from what I hear there are even more objects and columns in that one... / comments
Chris,
Sorry for the delayed response. It's been a busy couple of weeks and there isn't a slowdown in sight... That being said, here is the information you requested from our Production Database:...
Thanks for the help Chris.
I currently have SQL Prompt 5.3.4.1 installed. (Officially I'm still in the Trial period, but we have a PO that is being worked on for 10 people on our team. I'd like to have this worked out before we get it on everyone's machine.)
When I unload the databases, things continue to work until the next time I switch databases at which point I get the error message again. For the most part, I am able to use the Refactor product in between loads, however with SQL Prompt installed (and Display Suggestions turned off) I have to manually trigger the SQL Server Intellisense which is also cumbersome.
After playing with it a little more, I seem to have the biggest problems with using multiple databases at the same time. As long as I only use objects in the database that I am primarially connected to, it works pretty well. As soon as I try to compare data between databases for test validation, etc... I run into the Outof MemoryException.
With the Databases Unloaded I was able to successfully refactor, but I lost the ability to use snippits and auto insert object/column names through SQL Prompt or Intellisense. Opening a new query window allowed me to start getting suggestions again until the next time it unloaded databases. / comments
Thanks for the help Chris.
I currently have SQL Prompt 5.3.4.1 installed. (Officially I'm still in the Trial period, but we have a PO that is being worked on for 10 people on our team. I'd like t...
Constantly running out of memory
I've got SQL Prompt installed in Management Studio primarially for the functionality that used to be Refactor. I am working with PeopleSoft databases that each have over 29,000 Tables and 21,000 V...
Backup Jobs hang after first database
I just recently upgraded SQL Backup to version 6.4 and it is working on two of my servers. However on a 3rd (clustered) instance, the back up job is starting, but never runs to completion.
All of ...
Installing on SQL 2008
I have my first new SQL 2008 server, and I am working on getting SQL Backup installed. I'm running into a couple issues (quite possibly with my thought process) so I wanted to throw out what I was...
SQL Backup GUI doesn't close completely
I have run into this issue a few times recently, and finally have decided to ask about it.
Occasionally when I am using the GUI to look at backup results, or to run an individual backup, the applic...
Management Studio Integration
This is a feature request, so if I need to request this some where other than the forums, please let me know.
Would it be possible to integrate SQL Backup into SQL Management Studio like Red Gate h...
I am having a similar issue on one of my SQL 2005 Servers. We have databases that are in SIMPLE recovery occasionally attempt to perform LOG backups.
One slight difference is that we use BACKUP LOG EXCLUDE '...' where we explitly exclude a few databases that are on a separate plan. Since it works most of the time, I assume that it should work similar to the BACKUP LOG [*] command regarding SIMPLE databases that aren't explicitly excluded. I have double checked our DDL triggers and there haven't been any ALTER DATABASE commands run that would change the Recovery Model.
We are currently running on version 5.3.0.178. We're getting all of the backups we need, but it's a pain having to go out and look at the failures just to see that it fails on a database it shouldn't have even attempted.
Is there a new version that already includes this fix, or any word on when the next version will be released?
Thanks. / comments
I am having a similar issue on one of my SQL 2005 Servers. We have databases that are in SIMPLE recovery occasionally attempt to perform LOG backups.
One slight difference is that we use BACKUP LO...
Partial Cluster Install??
I just updated from SQL Backup 5.2 to 5.3. When installing on our 4 node Cluster, I selected the option to update all nodes, and provided the Cluster Admin username and password.
Everything in the...