Comments
Sort by recent activity
Hi rev,
When the trace option is turned on, the trace will be created in the default log directory for the SQL Server. If you connect to the instance in question using SSMS, choose Properties of the instance and Database Settings what is the value for Database default locations>Log: ?
Does this value look valid? If you could make sure that this value is valid and reachable by the SQL Server service/username, turning the trace flag back on should then work correctly.
If the value is accessible please get back to me and we will try something else.
Thanks, / comments
Hi rev,
When the trace option is turned on, the trace will be created in the default log directory for the SQL Server. If you connect to the instance in question using SSMS, choose Properties of t...
Hi Ken,
That sounds like an interesting idea so I have raised an enhancement request for it. The reference is SC-4570 and this will be considered for a future release. Thank you for your feedback. / comments
Hi Ken,
That sounds like an interesting idea so I have raised an enhancement request for it. The reference is SC-4570 and this will be considered for a future release. Thank you for your feedback.
Thank you for the update, if you want to send over the schema to help us try to track down the problem anyway that would be great. / comments
Thank you for the update, if you want to send over the schema to help us try to track down the problem anyway that would be great.
Hi aharbath,
Are you populating this table from another Database/Table by any chance? It looks as though SQL Data Generator might be trying to put blank data into a column which doesn't allow blank data. If this is from an existing Database/Table can you check to see if it has any blank rows for that column?
Thanks, / comments
Hi aharbath,
Are you populating this table from another Database/Table by any chance? It looks as though SQL Data Generator might be trying to put blank data into a column which doesn't allow blan...
Hi again,
Do you think it would be possible to provide us with a binary schema snapshot of the database so we can try to recreate here? You can use SQL Compare or the tool here to take your snapshot. If you could then e-mail it to support@red-gate.com with reference number F0028994 that would be great. / comments
Hi again,
Do you think it would be possible to provide us with a binary schema snapshot of the database so we can try to recreate here? You can use SQL Compare or the tool here to take your snapsh...
Hi coleman,
There isn't a command line validation as such although you could add the NOCOMPRESSWRITE or NOWRITE arguments so no the backup is actually simulated and no backup files are created.
I hope that helps, / comments
Hi coleman,
There isn't a command line validation as such although you could add the NOCOMPRESSWRITE or NOWRITE arguments so no the backup is actually simulated and no backup files are created.
I h...
Hi YoD@,
Could you please verify the SQL Backup Server Components version you are running and the SQL Backup Agent service account? The only other instance I have heard of this occurred was when the Network Service account was used. Could you try using a different account to what you are now and running a backup?
Thanks, / comments
Hi YoD@,
Could you please verify the SQL Backup Server Components version you are running and the SQL Backup Agent service account? The only other instance I have heard of this occurred was when t...
Hi maci,
Thank you for your forum post. This is a known issue with Dependency Tracker and a few of our other tools. Are you ok to keep the Print Spooler Service running or is that not an option for you?
(I actually posted this on Monday but it didn't seem to actual go up!)
Thanks, / comments
Hi maci,
Thank you for your forum post. This is a known issue with Dependency Tracker and a few of our other tools. Are you ok to keep the Print Spooler Service running or is that not an option for...
Hi Jerry,
SQL Backup does have the RESTORE FILELISTONLY, RESTORE HEADERONLY and RESTORE SQBHEADERONLY syntax which can be used as normal something like this:
EXECUTE master..sqlbackup '-SQL "RESTORE FILELISTONLY FROM DISK = ''E:\Backup\mybackup.sqb''"'
Info can also be found here at the bottom and here.
If using this as part of a script, you may also want to use the SINGLERESULTSET option so the details returned are easily readable by your script.
I hope that helps. / comments
Hi Jerry,
SQL Backup does have the RESTORE FILELISTONLY, RESTORE HEADERONLY and RESTORE SQBHEADERONLY syntax which can be used as normal something like this:
EXECUTE master..sqlbackup '-SQL "RESTOR...
Hi fatherjack,
OLR doesn't use the actual SQL Backup engine so any actions taken with OLR will not be recorded the same as SQL Backup jobs and appear on the time line or Activity History.
Hope that answers your question.
Thanks, / comments
Hi fatherjack,
OLR doesn't use the actual SQL Backup engine so any actions taken with OLR will not be recorded the same as SQL Backup jobs and appear on the time line or Activity History.
Hope that...