Comments
Sort by recent activity
Hi Greg,
Thanks for your post.
Doing a trace is probably the best way of getting the user information for the query. SQL Monitor should give you the query plan if you want more details, but my understanding is that you can't find the user from that.
You can also reduce the threshold on the long running query alert so that you get more of them. Those alerts should say the user in them.
Regards,
Evan / comments
Hi Greg,
Thanks for your post.
Doing a trace is probably the best way of getting the user information for the query. SQL Monitor should give you the query plan if you want more details, but my und...
Hello,
Thanks for your post.
You unfortunately can't see the seconds for the start time, but if you go into alert details, you should be able to see the start minute (listed as "Query start time") and the duration (listed as "Query duration").
Hope that helps.
Thanks,
Evan / comments
Hello,
Thanks for your post.
You unfortunately can't see the seconds for the start time, but if you go into alert details, you should be able to see the start minute (listed as "Query start time") ...
Hi Glycerine,
You're correct; I have also reproduced it with source controlled databases. I should have mentioned that in my last post.
Thanks,
Evan / comments
Hi Glycerine,
You're correct; I have also reproduced it with source controlled databases. I should have mentioned that in my last post.
Thanks,
Evan
Hi everyone,
Thanks for posting on this thread. This is actually a known bug with reference SC-7563 (it should only occur with a source control source). We have a fix for it which should be released when 11.1 comes out (which should be in the next two weeks or so).
Sorry about the inconvenience.
Regards,
Evan / comments
Hi everyone,
Thanks for posting on this thread. This is actually a known bug with reference SC-7563 (it should only occur with a source control source). We have a fix for it which should be relea...
Hi Andrew,
Thanks for your post.
SQL Compare can compare the schema of two databases and generate a script that will synchronize the target database to the source. For example, if you add a table to the source database, then run SQL Compare, it will generate a script with a "CREATE TABLE" statement you can run on the target.
It sounds like SQL Data Compare might be more what you're looking for -- this will look at the data within tables or views and compare that. So if your source table gets 30 rows added to it before you run SQL Data Compare, it will generate a script with 30 "INSERT" statements to run on the target. You can also do all of this from the command line, so you can schedule it for whenever you need.
That being said, it's not guaranteed to be faster than doing a backup and restore, because it can get decently expensive to look through every row in each of the tables you're comparing. I'd suggest doing some testing with our two week free trial.
Regards,
Evan / comments
Hi Andrew,
Thanks for your post.
SQL Compare can compare the schema of two databases and generate a script that will synchronize the target database to the source. For example, if you add a table ...
Hello,
Glad it seems to be working well.
You can contact sales@red-gate.com or go to this page: http://www.red-gate.com/dynamic/purchas ... sqlcompare
Thanks,
Evan / comments
Hello,
Glad it seems to be working well.
You can contact sales@red-gate.com or go to this page: http://www.red-gate.com/dynamic/purchas ... sqlcompare
Thanks,
Evan
Can you clarify what you mean by excluding schema? /exclude:schema will exclude objects of type schema from the comparison, but it will not exclude all objects in the schema. This article might be useful if you are trying to exclude all objects that match a certain form (like schemaname.x) : http://documentation.red-gate.com/displ ... ated+names
Thanks,
Evan / comments
Can you clarify what you mean by excluding schema? /exclude:schema will exclude objects of type schema from the comparison, but it will not exclude all objects in the schema. This article might b...
Hello,
You can use the /exclude:additional switch to make it so objects that only exist in the target aren't dropped.
Thanks,
Evan / comments
Hello,
You can use the /exclude:additional switch to make it so objects that only exist in the target aren't dropped.
Thanks,
Evan
Hello,
Unfortunately I can't think of a great way to use the exclude switch and have it scale if you add new objects in the future.
I just did a bit of testing with the /project switch, and it looks like you can do a compare in the UI, deselect the "objects that only exist in target" in the results pane, then save the project. When you call it using the /project switch from the command line, it will remember to exclude objects only in target regardless of new objects added or removed in the future. This way you can also get the functionality of the filter. (You won't have to use the /filter switch, it will be included in the logic of the /project switch).
Here's the documentation for the command line: http://documentation.red-gate.com/displ ... mmand+line
Hope that helps.
Thanks,
Evan / comments
Hello,
Unfortunately I can't think of a great way to use the exclude switch and have it scale if you add new objects in the future.
I just did a bit of testing with the /project switch, and it look...
Hello,
You should be able to do this with the following switch:
/Options:Default,IgnoreIndexes
Here's a list of options: http://documentation.red-gate.com/displ ... mmand+line
Regarding running the command for multiple databases, you'll need to use a utility other than our tool to run the command line script 500 times and change the value of /database2 for each one.
Hope that helps.
Thanks,
Evan / comments
Hello,
You should be able to do this with the following switch:
/Options:Default,IgnoreIndexes
Here's a list of options: http://documentation.red-gate.com/displ ... mmand+line
Regarding running the...