Your company has a main office in London and a branch office in New York.
Your network contains a server named Server5 that has SQL Server 2012 installed.
Serverscontains a database name ContentDB and a table named ContentTable.
You add an additional server named Server9 that runs SQL Server 2012.
You need to create a distributed partitioned view. The solution must minimize the amount of
network traffic.
What should you do? (Each correct answer presents part of the solution. Choose all that
apply.)
A.
Create the view on Server5.
B.
Add Server9 as a linked server.
C.
Create the view on Server9.
D.
Add the Customers table to Server9.
E.
Add Server9 as a Distributor.
F.
Remove the Customers table from Server5.
D-B-C
https://technet.microsoft.com/en-us/library/ms188299(v=sql.105).aspx
ABCD
Hello,
Ok
Note : the question has an issue, “ContentTable” should be “Customers”.
a+,=)
-=Clement=-
HR_OS_B, the link you provided says: “Creating a distributed partitioned view on each member server”
So maybe A-B-C-D is the correct answer?
I think it is ABCD
ABCD
Why C is necessary?
I think it is ABD
ABCD
B – Because partitioned tables are distributed across multiple servers, each server needs access to every other server. So, you need to configure all the servers as linked servers.
D- On each of the servers, create a table that has the same structure as the original table that you’re splitting.
A + C – Creating the partitioned views.
Now that you’ve set up the partitioned tables, you need to assemble them, which is probably the easiest part of the process. You define a view that assembles the rows from each table by using the UNION ALL operator. In each server, you have one local table and two remote tables, so the view looks slightly different in each server. You reference the local table by using only the table name, and you reference the remote tables by using the four-part table name, such as Node2.testdb.dbo.CustomersGP
Hope that helps.
AB CD apparently SO
After you create the member tables, you define a distributed partitioned view on each member server, with each view having the same name. This enables queries that reference the distributed partitioned view name to run on one or more of the member servers. The system operates as if a copy of the original table is on each member server, but each server has only a member table and a distributed partitioned view. The location of the data is transparent to the application.