Red Gate forums

RE: backuphistory table

petey — Tue, 07 Feb 2012 07:30:39 GMT

Yes, all backup attempts are logged here.

If you only want to report on successful backups, filter on the backup_set_uuid column. A non-empty value indicates a successful backup, and is a reference to the SQL Server backup_set_uuid column in the msdb..backupset table.

RE: Tab magic not visible in SSMS

pdevos — Tue, 07 Feb 2012 07:26:14 GMT

Hello Brian,

First of all, thank you for the reply.

When I take a look at the Tab Magic page on the Red-gate website I see a few screenshots. When you take a look at the following screenshot you'll see that in the upper left corner there is a button called "Recently closed tabs". Where can I find this button?

http://www.red-gate.com/products/sql-development/sql-prompt/entrypage/assets/images/sqltabmagic_recentlyclosed_large.png

Thanks in advance.

Smartassembly performance

noxe — Tue, 07 Feb 2012 00:38:17 GMT

'Non-schema statement was ignored' warnings

mjacobs — Mon, 06 Feb 2012 23:13:15 GMT

Some-how one of our developers has managed to edit and check in one of the schema files directly in the source control folder. The end result is a warning message every time we run a compare from source control.

I have identified the exact item that is causing this problem. It is actually one of our stored procedures but what also strange is that we have the same file suffixed with a 1;

dbo.up_kpi_salesmanager.sql
dbo.up_kpi_salesmanager1.sql

In the database we only have dbo.up_kpi_salesmanager.

It looks like the original file dbo.up_kpi_salesmanager.sql is no longer being used as dbo.up_kpi_salesmanager1.sql has more recent history.

I believe that my best cause of action is to stop the warning/error is to edit the offending file directly and correct the content. Another alternative could be to role back the change on the file and then reapply the correct update from the database.

However, before I try this I am wondering if the creation of the dbo.up_kpi_salesmanager1.sql file is expected behaviour and how can I 'merge' the 2 files back to a single file? I guess that there must be a file used by SQL Source Control to link a file to a database object?

-M

RE: "Unknown" Changed By Field

SteveGTR — Mon, 06 Feb 2012 22:48:42 GMT

We are choosing the shared environment because it reflects how we currently work.

In addition, I like that other developers can see what is being worked on by other developers.

That is why the "Unknown" changed by bug is so important to me.

In a perfect world the source control system we used would:

1) Manage the SQL scripts automatically for us --- RedGate does a great job with this

2) When someone is working on a SQL object others developers should be able to see that they are doing the work --- RedGate's shared model should do this, but the "Unknown" bug is causing this to fail

The reason why I feel it is important to communicate when a change is being made is because stored procedures don't merge well when two people are working on them at the same time. If someone sees that another person is working on a SQL object they can work more carefully. This avoids duplication of effort, wasted effort, and errors.

Don't get me started... oh! Too late

RE: "Unknown" Changed By Field

SteveGTR — Mon, 06 Feb 2012 22:41:46 GMT

Thanks for the reply David.

I'm actually looking for a response from someone who uses your product with the shared database model in a team environment.

RE: "Unknown" Changed By Field

David Atkinson — Mon, 06 Feb 2012 22:13:29 GMT

Hi Steve,

Thanks for your question. The reason the default trace is used is because it is enabled by default (thereby requiring no additional configuration) and supplies us with the information we need. The challenge is that the default trace will roll over, and for some users too quickly. 15 minutes is very quickly.

We're currently investigating alternatives, including persisting this in our own data store. The drawback is that this requires DBAs to administer yet another database, which is an implementation that could be too intrusive for some, but it could be the only option.

I hope this answers your question. We'll be aiming to release on a more frequent cycle, so hopefully we'll be able to further improve what is understandably a popular feature.

Out of interest, what is the reason you are choosing a shared development environment over dedicated per-developer ones?

David Atkinson
Product Manager
Red Gate

RE: "Unknown" Changed By Field

SteveGTR — Mon, 06 Feb 2012 21:53:00 GMT

I give up... Does anyone use the shared database model? If so, how are you handling the "Unknown" changed by problem?

It's hard for me to understand how this product can be used in a multi-developer environment when the changed by field goes out of scope (becomes "Unknown") in such a short time frame. In our case, 15 minutes and all the pending changes come up as "Unknown".

Why RedGate would implement such an unreliable technique as the default trace for the changed by field is beyond my comprehension. Maybe someone could explain it to me.

Thanks

RE: SSMS crashing after upgrade to 3.0.5.7

gvarol@corelogic.com — Mon, 06 Feb 2012 20:38:31 GMT

Any update on this issue ???

RE: Restore encypted SQB issue

reulberg — Mon, 06 Feb 2012 19:51:05 GMT

Interesting...

When I first encountered this error I was using the gui, and the gui doesn't allow one to proceed past file selection.

When manually executing a script, it throws the same error, but completes with a usable DB...

Requested info emailed.