Comments
Sort by recent activity
Brian Donahue wrote:
Hi Mark,
It sounds like SQL Server is returning this error - are you checking both the server platform version as well as the compatibility level of the database itself?
Never thought to check compatibility level. Will take a look next time I connect / comments
Brian Donahue wrote:
Hi Mark,
It sounds like SQL Server is returning this error - are you checking both the server platform version as well as the compatibility level of the database itself?
N...
Hi Steve
I did try that with one of the DB's but it wanted tme to drop a ton of stuff.
Tried again this monring and it worked fine
Thanks for answer
Regards
Mark / comments
Hi Steve
I did try that with one of the DB's but it wanted tme to drop a ton of stuff.
Tried again this monring and it worked fine
Thanks for answer
Regards
Mark
peter.peart wrote:
Thanks for your post. You're going to need a separate repo for each DB, I'm afraid.
Pete
Thanks Pete
Not a problem. Will just group them under a single folder / comments
peter.peart wrote:
Thanks for your post. You're going to need a separate repo for each DB, I'm afraid.
Pete
Thanks Pete
Not a problem. Will just group them under a single folder
Thanks chris
i'll see how my DB frows on the regular 2008 server and see how long it will take to get to 4GB / comments
Thanks chris
i'll see how my DB frows on the regular 2008 server and see how long it will take to get to 4GB
DIdn't work. Synonyms are at table level. Got way too many to use / comments
DIdn't work. Synonyms are at table level. Got way too many to use
Hi David
Is a post-deployment script a red-gate thing? I tried searching support site and didn't find anything.
Can you give me a hint how I'd do such a thing. Let's assume I have an SP in QA_Planning that I'm going to edit and this selects data from QA_Orders and QA_Customers. From what I understand, I would deploy this to Live_Planning and then run this post deployment script. unless it's part of red-gate, I would imaging that it'll be tricky to get all the objects it uses in other DB's
Regards
Mark / comments
Hi David
Is a post-deployment script a red-gate thing? I tried searching support site and didn't find anything.
Can you give me a hint how I'd do such a thing. Let's assume I have an SP in QA_Plann...
Hi David
You can ignore most of last post. Just discovered what synonyms are! (never come across them before). Seems they would solve it, but begs a different question - why would I need a post deployment script if I use these?
Regards
Mark / comments
Hi David
You can ignore most of last post. Just discovered what synonyms are! (never come across them before). Seems they would solve it, but begs a different question - why would I need a post dep...
Thanks David
from my quick reading (for anyone else who reads this). i can create a synonym called "Order" in both DB's and then I don't need any prefix: Orders will point to correct DB's (assuming the deployment process doesn't resolve synonyms to their targets).
Will have a play and post back
Regards
Mark / comments
Thanks David
from my quick reading (for anyone else who reads this). i can create a synonym called "Order" in both DB's and then I don't need any prefix: Orders will point to correct DB's (assuming...
Hi David
Will give it a go with polling turned off. Just concerned that I won't see my colleague has soemthing checked out and I start working on it
Regarding this:
"Or use synonyms for all cross-database references and have a script that changes the synonyms when you deploy to production"
The changes would be easy because it simply swapping "QA_" for "Live_". Could the script be run automatically as part of deploy?
Regards
Mark / comments
Hi David
Will give it a go with polling turned off. Just concerned that I won't see my colleague has soemthing checked out and I start working on it
Regarding this:
"Or use synonyms for all cross-d...
Hi David
Thanks for the reply. We could only maintain a dev DB is if it's on a different SQL Intance/Server because the vendor-supplied application we use has 7 connected db's and a lot of cross-db queries. We currently have 3 sets: Live_, QA_, Test_, but it's a pain to work like this. If we develop in QA_, all cross db statements begin with QA_ and we have to remember to change them to Live_ before deploying (which would have to be a manula process).
Obviously, we could do what we wnat with DB's, etc. But the license for the vendor's app wouldn;t work if we used a difference instance name, so we wouldn;t be able to test effects of our changes
Right now, even if we wanted to we couldn't use a new instance because of memory constraints on server, but a new server is being commisioned in a few months
Am I missing something, or do you see an alternative to this?
One last question: does the filter reduce the polling volume, or just what we see?
Regards
Mark / comments
Hi David
Thanks for the reply. We could only maintain a dev DB is if it's on a different SQL Intance/Server because the vendor-supplied application we use has 7 connected db's and a lot of cross-db...