Comments
Sort by recent activity
Thanks for the notification.
Nick / comments
Thanks for the notification.
Nick
That definitely helped. Thanks.
Nick / comments
That definitely helped. Thanks.
Nick
I executed the following:
EXECUTE master..sqbutility 999, 'RWE', 'C:\Program Files\Red Gate\SQL Backup 6\(LOCAL)'
Response is:
<SQBUTILITYRESULT>:1:
This result says the read/write permissions on the log folder are ok.What next? / comments
I executed the following:
EXECUTE master..sqbutility 999, 'RWE', 'C:\Program Files\Red Gate\SQL Backup 6\(LOCAL)'
Response is:
<SQBUTILITYRESULT>:1:
This result says the read/write permissions on t...
I received an email from support and am copying my reply here:
I ran the following as a diagnostic:
EXECUTE master..sqbutility 9997
I ran this but there is no bug report in C:\Program files\Red Gate\SQL Backup 6\%instance% folder. It returns NULL with the message "1 record affect". No text files at all in this folder. Could it be somewhere else?
I've had to kill the SQL Backup process via Services several times when the backup hung and the server has not been rebooted. Could that be contributing to sqbutility not reporting properly?
I also ran EXEC master..sqbstatus and it reports the following. None of it changes. BACKUP VERIFY statement is still hung.
Database Login Processed (bytes) Compressed (bytes)
NULL DOMAIN\Administrator 2578448384 499648512
Nick / comments
I received an email from support and am copying my reply here:
I ran the following as a diagnostic:
EXECUTE master..sqbutility 9997
I ran this but there is no bug report in C:\Program files\Red Gat...
I ended up rebooting the machine and that seemed to have fixed it. I thought I posted that somewhere.
Regards,
Nick
Brian Donahue wrote:
Hi Nick,
I would recommend, firstly, manually uninstalling SQL Backup 5.x from the servers that you want to upgrade using Windows add/remove programs, then run the SQBServerSetup.exe from the SQL Backup 6 installation directory manually on the server.
As far as I can tell, the mutex used in version 6 is no longer "Global", so I would assume that the SQL Backup Agent Service on this instance is still version 5.
When running SQBServerSetup, I believe that you include the instance name in the command, ie: SQBServerSetup.exe /I "MyInstance".
/ comments
I ended up rebooting the machine and that seemed to have fixed it. I thought I posted that somewhere.
Regards,
Nick
Brian Donahue wrote:
Hi Nick,
I would recommend, firstly, manually uninstalling ...
I have VS Studio 2005 installed and have access to 2008 if need be.
I'm also taking the occasion to push the folks dragging their feet on upgrading our code to make it SQL 2008 compatible. We've got old style sql-92 joins littered everywhere.
Thanks,
Nick
Simon C wrote:
It looks like SQL Compare is obtaining wrong version information from the connection information with the server. Do you have access to visual studio you can run a small console app with?
/ comments
I have VS Studio 2005 installed and have access to 2008 if need be.
I'm also taking the occasion to push the folks dragging their feet on upgrading our code to make it SQL 2008 compatible. We've go...
Any word on this? When I script a folder out is always seems to include the PAD_INDEX ON text (which is incorrect) regardless of the setting to ignore fillfactor and pad_index settings and then it errors when I try to do a compare.
Thanks,
Nick
NDUCKSTE wrote:
Makes sense. Running SQL 2005 SP3, but database is in 8.0 compatability mode. The error comes from SQL Compare when the scripts first get created via the command line. Should I be doing any thing different?
Simon C wrote:
PAD_INDEX is SQL 2000 syntax, PAD_INDEX = ON is SQL 2005/8 syntax. What version of SQL Server are you running the script on, and what's the compatability mode of the database?
/ comments
Any word on this? When I script a folder out is always seems to include the PAD_INDEX ON text (which is incorrect) regardless of the setting to ignore fillfactor and pad_index settings and then it ...
Figured out the filter switch like you suggested, i.e. create a filter file via the UI and then reference it with the /filter: switch.
However, that hardcodes and XML filter file with specific search criteria. I want my criteria parameterized, not hardcoded. In other words, I can't create a filter file for a every different flavor of a parameter I might encounter -- I simply don't know what all the parameters are in advance.
Part of my confusion is why I would need the /filter: statement at all. The documentation on include/exclude states that the parameters for these switches are regular expressions:
/include:<object type>:<regular expression>
Thanks in advance,
Nick
NDUCKSTE wrote:
One more question. You reference the /filter: switch. I see it referenced on the command line when I type sqlcompare /? but I don't see any examples about how to use it on the online docs.
Do you have any documentation on how to use the /filter: switch?
Thanks,
Nick
/ comments
Figured out the filter switch like you suggested, i.e. create a filter file via the UI and then reference it with the /filter: switch.
However, that hardcodes and XML filter file with specific sear...
One more question. You reference the /filter: switch. I see it referenced on the command line when I type sqlcompare /? but I don't see any examples about how to use it on the online docs.
Do you have any documentation on how to use the /filter: switch?
Thanks,
Nick
Chris Auckland wrote:
Thanks for your post.
You don't need to do anything special to include all tables containing Log.
The first example (/Include:table:Log) should include tables:
Log
LogA
LogB
New_Log
If you only want a specific table, i.e. 'LogTest' you will need to use:
/Include:table:\[LogTest\]
If are looking to only include tables with a certain schema/owner, i.e.
Log.Table_A
Log.Table_B
Then you will need to add a filter for the 'Log' schema/owner to the project. You can create a filter through the UI, and then reference it through the command line using /filter:
I hope this is helpful.
/ comments
One more question. You reference the /filter: switch. I see it referenced on the command line when I type sqlcompare /? but I don't see any examples about how to use it on the online docs.
Do you h...
Makes sense. Running SQL 2005 SP3, but database is in 8.0 compatability mode. The error comes from SQL Compare when the scripts first get created via the command line. Should I be doing any thing different?
Simon C wrote:
PAD_INDEX is SQL 2000 syntax, PAD_INDEX = ON is SQL 2005/8 syntax. What version of SQL Server are you running the script on, and what's the compatability mode of the database?
/ comments
Makes sense. Running SQL 2005 SP3, but database is in 8.0 compatability mode. The error comes from SQL Compare when the scripts first get created via the command line. Should I be doing any thing d...