hey,

hold on - wasn't this why hierarchyID types were invented ?

you can even use persisted computed columns to make it nice and fast.

you would need a 1 time...

ok here is the most basic stuff you need - the rest you can google and find lots of cool code

CREATE TABLE #htest (id INT IDENTITY, hierarchyvalue...

might take me a little while just to pull all of the examples and test data together - it's 2 pm and I've not had lunch yet... my laptop is...

my advice - simplify the connection/session thing into SPIDs - much more useful.

quite often a connection will remain idle and the SPID does nothing (this gets more complicated when connection...

you can have many snapshots of a database , they work in the same way as oracle - if you change data in the live data then the old data...

Thanks guys.   I'll check out mirroring as I have enterprise.

how about having a check to say   "Is the subscriber database the same as the publishing database"

I might be able...

hey,

hold on - wasn't this why hierarchyID types were invented ?

you can even use persisted computed columns to make it nice and fast.

you would need a 1 time hit on...

SSRS is fairly solid for this

you can subscribe to reports (and get them emailed to you) and keep historic versions on the server... plus you can export in excel, pdf...

most likely you have a few  solutions here

1. lock down the permissions on the subscriber database so that only the distribution agent can write, but everyone else has read permissions

...

Any slowdown would be on your T-Log drive (the commands are read from t-log and pushed to the distributor database) - if replication fails, then you might get some issues...

Rod,

perhaps I can help - I have about 30 or more azure devops repositories that we use. but I've never hit a warning about publishing email addresses. can you give...

I run transactional replication all day every day (to get around linked server performance issues)

performance won't be an issue, but as soon as your subscriber (target) has data deleted, modified...

back to KTFlash's comment about "everything already documented"

I was listening to a stereophonics song the other night and the song was called "a thousand trees"

The more I listened, the more...

I think what put me off XE was the initial documentation and the user interface for the results (creating an XE trace is almost the same as profiler) but viewing...

I did also say extended events 🙂

but look how useful profiler is !!!!!! 15 seconds of capture while my user re-creates...