Comments
Sort by recent activity
Thanks for letting us know it's working ok now! / comments
Thanks for letting us know it's working ok now!
Thanks for your query!
Unfortunately this isn't supported right now.
There is a workaround however: Create a comparison project in SQL Data Compare containing the databases you want to compare and any table mappings and WHERE clause, then right-click it, select 'locate on disk', and make a copy of the project file in another location on disk.
Next, use SQLDataCompare.exe to run the project using the /pr argument. The command-line version of SQL Data Compare can use the where clause that you'd set in the project.
I've checked at this end, and currently it looks like the WHERE clause will be supported in version 9 at some point, although this is subject to change of course. / comments
Thanks for your query!
Unfortunately this isn't supported right now.
There is a workaround however: Create a comparison project in SQL Data Compare containing the databases you want to compare and ...
Aah, I see - so windows auth is indeed enterprise only: http://www.visualsvn.com/server/feature ... integrated / comments
Aah, I see - so windows auth is indeed enterprise only: http://www.visualsvn.com/server/feature ... integrated
SQL Source Control should work fine with Standard.
I'm guessing the message you're seeing is some "left-over" from you previously having it working as an Enterprise version.
If you try accessing the location you're linked to with Tortoise SVN, does it work okay? Can you try unlinking + relinking your database from within SSMS to see if it then starts working? / comments
SQL Source Control should work fine with Standard.
I'm guessing the message you're seeing is some "left-over" from you previously having it working as an Enterprise version.
If you try accessing th...
Hi,
The alert won't occur immediately after the time set - all that controls is how long the query must be running before it generates an alert.
The actual polling frequency is configured via an XML file (if you do want to change it - bearing in mind more frequent polling may affect server performance).
If you look for "config.xml" (mine is in C:\Program Files (x86)\Red Gate\SQL Response 1\Alert Repository) you'll see a line containing:
- <!-- This will affect the polling frequency for these alerts; Long running query and Blocked SQL Process - setting to every 45 seconds
-->
<SysProcessesTime>45</SysProcessesTime>
This means that the check will be made every 45 seconds; which is why the alert occurs in the way you see. i.e. the query lasted longer than 10 seconds so will trigger the alert, and was still going after 45 seconds, so you get that in the alert detail.
Hope that helps. / comments
Hi,
The alert won't occur immediately after the time set - all that controls is how long the query must be running before it generates an alert.
The actual polling frequency is configured via an XM...
Hi Daniel,
You can put standard connection string commands in the Server name box. So for example, the following should do what you need (obviously replacing the xxx with the packet size figure you need)
ServerName\Instance;Packet Size=xxxxx / comments
Hi Daniel,
You can put standard connection string commands in the Server name box. So for example, the following should do what you need (obviously replacing the xxx with the packet size figure you...
Thanks for this suggestion. I can see how it would be handy, so I'll pass it on to our development team for evaluation.
James / comments
Thanks for this suggestion. I can see how it would be handy, so I'll pass it on to our development team for evaluation.
James
Hi there.
SQL 2008 shouldn't present an issue - certainly my test servers are found.
Have you tried scrolling to the bottom of the list and clicking "Add SQL Server instance", then putting in the FQDN or the IP address of the relevant server? / comments
Hi there.
SQL 2008 shouldn't present an issue - certainly my test servers are found.
Have you tried scrolling to the bottom of the list and clicking "Add SQL Server instance", then putting in the F...
Hi John,
This feature is something that has been asked for previously, and will hopefully make it in to a future release of the product.
For now, there is a workaround that may be of use to you:
- Add your new column(s)
- Create a copy of the table you are interested in using something along the lines of: SELECT *
INTO temptable
FROM sourcetable
- In SQL Data Generator, choose the option to "Use Existing data source" for the table you are working with. Source Type is "SQL Table or View", and the Source is the copy you made (temptable in the above example)
- Expand the table in the tree on the left, and for the new columns, select the generator you wish to use.
- Confirm the other columns are correctly referring to the source temp table.
- With the table itself selected on the left, ensure you have "Same as mapped data" set in the Specify number of rows box.
- You still need to have "Delete data from table before generation" ticked, otherwise you will just get twice the number of records (or it will fail with duplicate keys) and you may also need to temporarily remove foreign key constraints if it warns you the delete could fail.
Hopefully the above will achieve the effect you are after, but if not, please feel free to contact support.
James. / comments
Hi John,
This feature is something that has been asked for previously, and will hopefully make it in to a future release of the product.
For now, there is a workaround that may be of use to you:
- ...
I just tried following your reproduction steps myself, but I couldn't get the error - can you check you're running the latest patch from here? If you still have trouble I can check it out some more. / comments
I just tried following your reproduction steps myself, but I couldn't get the error - can you check you're running the latest patch from here? If you still have trouble I can check it out some more.