Best Of
Re: Changing the version controlled database - anything to be aware of?
In theory you should be using source control in dev, not production. You should be deploying to production from source control, not retrospectively commiting changes to source control after they have been applied in prod. If what you are looking for is an audit log of changes you should look at DLM Dashboard instead.
With regards moving your source control to the pre-prod DB, the simple answer is to use something like SQL Compare to sync yp the schemas and then unlink prod and link pre-prod.
But as I mentioned, you really you should be doing that all the way down to dev and then using source code as the source of truth for all deployments to your test/pre-prod/prod dbs.
With regards moving your source control to the pre-prod DB, the simple answer is to use something like SQL Compare to sync yp the schemas and then unlink prod and link pre-prod.
But as I mentioned, you really you should be doing that all the way down to dev and then using source code as the source of truth for all deployments to your test/pre-prod/prod dbs.
AlexYates
2 ·
Improved analyzer support for generics?
Are there any plans for adding analyzer support of generic type arguments and constraints in the Reflector roadmap? At present, the "used by", "exposed by", and "instantiated by" analyzers will locate types and members based on generic type definition, but the results do not include uses of the focal type as a generic type argument or a generic type constraint.
This has been a non-trivial gap in Reflector functionality for quite some time, and it has become increasingly problematic since async started becoming more prevalent (and everything started being wrapped in a Task<>). For example, if I'm looking for uses or exposure of a type Foo, I won't be able to find IEnumerable<Foo> or Task<Foo> uses under the current analyzer implementations.
Thanks,
Nicole
This has been a non-trivial gap in Reflector functionality for quite some time, and it has become increasingly problematic since async started becoming more prevalent (and everything started being wrapped in a Task<>). For example, if I'm looking for uses or exposure of a type Foo, I won't be able to find IEnumerable<Foo> or Task<Foo> uses under the current analyzer implementations.
Thanks,
Nicole
nicole_c
1 ·
PE006 (TABLE HINT is used)
Would like this to be more granular.
When doing reporting I use the WITH (NOLOCK) to avoid locks on tables.
I would like to be able to disable specific warnings about specific hints.
When doing reporting I use the WITH (NOLOCK) to avoid locks on tables.
I would like to be able to disable specific warnings about specific hints.
BrienKing
2 ·
Re: Which Windows Server versions and MSSQL versions does SQL Backup ver 9.2.1.128 support?
Hi @sbs
Thanks for your post.
You can find all of the information on the release notes and documentation for SQL Backup in my linkn below.
https://documentation.red-gate.com/sbu9/release-notes-and-other-versions
Kind regards
Thanks for your post.
You can find all of the information on the release notes and documentation for SQL Backup in my linkn below.
https://documentation.red-gate.com/sbu9/release-notes-and-other-versions
Kind regards
RichardL
1 ·
Re: Managed Develop & Stage environments with a shared database model
One thing you could do is select the dedicated option even though you are using shared. For various complicated technical reasons it will probably work fine. In order to explain that it might be worth actually scheduling a skype call to talk through it.
However, it's ugly and smelly and you should just move to the dedicated model.
However, it's ugly and smelly and you should just move to the dedicated model.
AlexYates
1 ·
Re: Not getting update scripts from DLM release
Maybe this is a silly question, but have you made any changes or are the source package and target database already in an identical state?
AlexYates
1 ·
