Viewing 15 posts - 16 through 30 (of 52 total)
We'd use a not dissimilar approach for creating test data and removing sensitive data when copying from production to development. Each of the tables had a corresponding table in a...
November 17, 2015 at 9:15 am
Yeah, I found a lot more since I first posted. For example, from the master server:
selectserver_name, *
frommsdb.dbo.systargetservers
or this, to help identify target servers that are failing:
-- http://mikehillwig.com/tag/multi-server-administration/
create table #tmp_sp_help_targetserver(
server_id int...
September 21, 2015 at 8:42 am
You're right. I should have expanded on this. The archive data would be exported to a database on another server. If that is not possible, then an export to a...
August 17, 2015 at 9:56 am
You may also free up some space with a more aggressive archiving approach to your data, or install archiving at all.
I've seen a number of legacy systems have up 10...
August 17, 2015 at 9:34 am
I've had much better luck historically by creating a [font="Courier New"]#TempTable[/font] with a [font="Courier New"]Done = cast(0 as bit)[/font] extra column.
That way I can review the results at the end...
June 1, 2015 at 10:53 am
I didn't have any success with Adam Haines' approach. When trying to test this I got the error:
[font="Courier New"]The specified schema name "dbo" either does not exist or you do...
May 26, 2015 at 6:25 pm
I very much appreciated the connection and feedback about Rob's article. I have felt that way at times, too, but never really had the means to discuss my REALLY strong...
April 20, 2015 at 10:06 am
This was some great code, Jack. Much of it is working well. However, the cdc_DBName_capture job is taking a heck of a long time. It needs about 18 hours of...
February 24, 2015 at 6:47 pm
The best answer I've had for keeping the LDF and MDFs for system databases in the same directory is that they're that way by default on install and there's no...
November 17, 2014 at 4:37 pm
Not so much. It seems that all the Change Data Capture stuff is a "push" to the destination.
I was hoping that it would be more like replication where the Subscriber...
October 17, 2014 at 9:42 am
We've had good success lumping similarly used tables and procedures into schemas and then creating a role for the schema and assigning "User" permissions to the role, specifically SELECT, INSERT,...
October 15, 2014 at 11:11 am
I remember doing this as well. Created a bunch of views in a separate schema that the users had access to. The views had friendly column names and made it...
September 25, 2014 at 9:18 am
In many ways, that would be true. But they didn't wan't to write a new package, or add to an additional one, every time they have new SQL. Doesn't really...
September 24, 2014 at 4:54 pm
Agreed about scanning existing permissions. I had considered adding this to the article but it was already getting lengthy. Plus there are a ton of postings on how to do...
July 30, 2014 at 1:10 pm
We also used AD groups in this implementation. The system is set up in such a way that any approach is possible. It can grow or shrink as needs arise....
July 30, 2014 at 8:50 am
Viewing 15 posts - 16 through 30 (of 52 total)