Comments
Sort by recent activity
Hi Ben- I might need a little clarification on your exact setup. Shared mode is indeed intended to be used when one set of files in TFS maps back to one single database that is used by several developers at once.
If you have a few different SQL Servers, each having their own copy of the database, and these are all linked to the same TFS location, then that is "dedicated" mode. I can't quite tell if that's exactly the case from your post though...
In general, we show the blue blob when we detect a change to an object (by picking up an entry from tempdb, as you mentioned).
When you refresh the Commit tab, a full comparison between the database and the working base folder is performed and the blue blobs and commit tab will update according to whatever differences are picked up. This article which explains the architecture may help a bit: SQL Source Control architecture / comments
Hi Ben- I might need a little clarification on your exact setup. Shared mode is indeed intended to be used when one set of files in TFS maps back to one single database that is used by several deve...
There's a lot of reasons for seeing "unknown".
If you've not changed the configuration in any way, then we read the information from the default trace in SQL Server. This can roll over alarmingly regularly on a busy server, at which point we cannot retrieve the information, so you see "unknown".
The trace also requires SA permissions to read it I believe, so this would also be a possible cause.
To overcome some of these issues you can configure a separate database to log changes. See http://documentation.red-gate.com/displ ... +databases
Note that some changes don't get marked in the trace at all, and will always show unknown. There's a list at the bottom of the page linked above. / comments
There's a lot of reasons for seeing "unknown".
If you've not changed the configuration in any way, then we read the information from the default trace in SQL Server. This can roll over alarmingly r...
Hi,
The most likely cause of the changed-by column not being there is if you linked up with the "dedicated" option set. When working in dedicated mode, we assume you are the only user of the database and the column is not shown.
If you're actually using shared mode, where you work on the same DB as others, then you just need to unlink and relink selecting "shared".
For full details on the differences, see here / comments
Hi,
The most likely cause of the changed-by column not being there is if you linked up with the "dedicated" option set. When working in dedicated mode, we assume you are the only user of the databa...
I'm pretty sure you can't easily get around this as we use the name we obtain from the instance when we query it?
But I'd suggest initially editing your linkeddatabases.xml file (in c:\users\<your username>\appdata\local\red gate\sql source control 3) to see if replacing the server name with the IP address for each linked DB helps. @SERVERNAME" against the server or similar, which will return the name rather than IP? Worth trying though! / comments
I'm pretty sure you can't easily get around this as we use the name we obtain from the instance when we query it?
But I'd suggest initially editing your linkeddatabases.xml file (in c:\users\<your ...
Hi there,
I think last time we saw this kind of behaviour it was because the server names matched up, even though you were accessing them via different IP addresses. Do you know if this is the case for you? / comments
Hi there,
I think last time we saw this kind of behaviour it was because the server names matched up, even though you were accessing them via different IP addresses. Do you know if this is the case...
Thanks for your post. I've just tried this in the latest release and I get a different error- but this may be down to me not having all the other objects that procedure needs.
It looks like some issues relating to MERGE were resolved in v10.2 of the SQL Compare engine, so ideally, you'd need to update to the latest 3.x release of SQL Source Control to see if that resolves it. / comments
Thanks for your post. I've just tried this in the latest release and I get a different error- but this may be down to me not having all the other objects that procedure needs.
It looks like some is...
Sure thing- if you're still having trouble, please do post back and we can do some more digging! / comments
Sure thing- if you're still having trouble, please do post back and we can do some more digging!
Hi Miron.
To generate data in just one column, you would highlight the table on the left hand side, then pick "Use existing data source" and point it at the table containing the data you want to keep in another DB.
Then, for each column, you can pick the source data to keep from the top of the "Generator" dropdown list, apart from the column you want random data for. For that column, just pick the generator you want.
The issue I think you will have is that the Weighted List generator doesn't allow you to base it on information from other columns/data - it only works with the data you put into the generator. / comments
Hi Miron.
To generate data in just one column, you would highlight the table on the left hand side, then pick "Use existing data source" and point it at the table containing the data you want to ke...
I'm afraid StarTeam isn't one I know of anyone using, but that doesn't mean it's not possible...
You do have the option of linking to a "Working Folder" when you link your database. You can then source control the working folder you choose and manually commit/update that from your repo using whatever tools you're already familiar with? / comments
I'm afraid StarTeam isn't one I know of anyone using, but that doesn't mean it's not possible...
You do have the option of linking to a "Working Folder" when you link your database. You can then so...
Just to follow up; I believe this issue was caused by trying to activate using a local account on a machine that's a member of a domain. This /shouldn't/ cause a problem, but may be useful if anyone else runs into it. / comments
Just to follow up; I believe this issue was caused by trying to activate using a local account on a machine that's a member of a domain. This /shouldn't/ cause a problem, but may be useful if anyon...