You are the administrator of a SQL Server 2000 computer at your company's
warehouse. All product orders are shipped from this warehouse. Orders are
received at 30 sales offices. Each sales office offers a range of products
specific to its region.
Each sales office contains one SQL Server 2000 computer. These servers
connect to the warehouse through dial- up connections as needed, typically
once a day. Each sales office needs data pertaining only to its region. You
need to replicate inventory data from the server at the warehouse to the
servers at the sales offices. You want to minimize the amount of time needed
to replicate the data. Which three actions should you take? (Each correct
answer represents part of the solution. Choose three.)
A. Create one publication for each Subscriber.
B. Create one publication for all Subscribers.
C. Enable horizontal filtering.
D.Enable vertical filtering.
E. Use pull subscriptions.
F. Use push subscriptions.
pls. help.
I would create one pub for all subscribers, do horizontal filtering ( so
only the data a subscriber needs would be sent.), and go with pull
subscriptions ( because the work would be done at the subscriber, not at the
publisher)..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Eric" <Eric@.discussions.microsoft.com> wrote in message
news:069B5539-A863-446C-9D04-C6879CA20E5B@.microsoft.com...
> You are the administrator of a SQL Server 2000 computer at your company's
> warehouse. All product orders are shipped from this warehouse. Orders are
> received at 30 sales offices. Each sales office offers a range of products
> specific to its region.
> Each sales office contains one SQL Server 2000 computer. These servers
> connect to the warehouse through dial- up connections as needed, typically
> once a day. Each sales office needs data pertaining only to its region.
You
> need to replicate inventory data from the server at the warehouse to the
> servers at the sales offices. You want to minimize the amount of time
needed
> to replicate the data. Which three actions should you take? (Each correct
> answer represents part of the solution. Choose three.)
> A. Create one publication for each Subscriber.
> B. Create one publication for all Subscribers.
> C. Enable horizontal filtering.
> D.Enable vertical filtering.
> E. Use pull subscriptions.
> F. Use push subscriptions.
> pls. help.
Showing posts with label product. Show all posts
Showing posts with label product. Show all posts
Wednesday, March 28, 2012
Question about querying database with select statement in SQL Server 2005
In the sql server 2005, why do I need to perform querying as followed
"SELECT * FROM Productiion.Product"
Why do i need to stick the prefix Production to the table named
"product" in Adventurework sample database?
Any idea would be appreciate.
Optimus wrote:
> In the sql server 2005, why do I need to perform querying as followed
> "SELECT * FROM Productiion.Product"
> Why do i need to stick the prefix Production to the table named
> "product" in Adventurework sample database?
> Any idea would be appreciate.
SQL Server 2005 uses the concept of schemas. That is, objects are owned
by schemas, and not users as they have been in the past. The separation
is beneficial. See "User-Schema Separation" in the SQL 2005 BOL for more
information.
David Gugick
Quest Software
www.imceda.com
www.quest.com
"SELECT * FROM Productiion.Product"
Why do i need to stick the prefix Production to the table named
"product" in Adventurework sample database?
Any idea would be appreciate.
Optimus wrote:
> In the sql server 2005, why do I need to perform querying as followed
> "SELECT * FROM Productiion.Product"
> Why do i need to stick the prefix Production to the table named
> "product" in Adventurework sample database?
> Any idea would be appreciate.
SQL Server 2005 uses the concept of schemas. That is, objects are owned
by schemas, and not users as they have been in the past. The separation
is beneficial. See "User-Schema Separation" in the SQL 2005 BOL for more
information.
David Gugick
Quest Software
www.imceda.com
www.quest.com
Question about querying database with select statement in SQL Server 2005
In the sql server 2005, why do I need to perform querying as followed
"SELECT * FROM Productiion.Product"
Why do i need to stick the prefix Production to the table named
"product" in Adventurework sample database?
Any idea would be appreciate.Optimus wrote:
> In the sql server 2005, why do I need to perform querying as followed
> "SELECT * FROM Productiion.Product"
> Why do i need to stick the prefix Production to the table named
> "product" in Adventurework sample database?
> Any idea would be appreciate.
SQL Server 2005 uses the concept of schemas. That is, objects are owned
by schemas, and not users as they have been in the past. The separation
is beneficial. See "User-Schema Separation" in the SQL 2005 BOL for more
information.
David Gugick
Quest Software
www.imceda.com
www.quest.com
"SELECT * FROM Productiion.Product"
Why do i need to stick the prefix Production to the table named
"product" in Adventurework sample database?
Any idea would be appreciate.Optimus wrote:
> In the sql server 2005, why do I need to perform querying as followed
> "SELECT * FROM Productiion.Product"
> Why do i need to stick the prefix Production to the table named
> "product" in Adventurework sample database?
> Any idea would be appreciate.
SQL Server 2005 uses the concept of schemas. That is, objects are owned
by schemas, and not users as they have been in the past. The separation
is beneficial. See "User-Schema Separation" in the SQL 2005 BOL for more
information.
David Gugick
Quest Software
www.imceda.com
www.quest.com
Question about querying database with select statement in SQL Server 2005
In the sql server 2005, why do I need to perform querying as followed
"SELECT * FROM Productiion.Product"
Why do i need to stick the prefix Production to the table named
"product" in Adventurework sample database?
Any idea would be appreciate.Optimus wrote:
> In the sql server 2005, why do I need to perform querying as followed
> "SELECT * FROM Productiion.Product"
> Why do i need to stick the prefix Production to the table named
> "product" in Adventurework sample database?
> Any idea would be appreciate.
SQL Server 2005 uses the concept of schemas. That is, objects are owned
by schemas, and not users as they have been in the past. The separation
is beneficial. See "User-Schema Separation" in the SQL 2005 BOL for more
information.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com
"SELECT * FROM Productiion.Product"
Why do i need to stick the prefix Production to the table named
"product" in Adventurework sample database?
Any idea would be appreciate.Optimus wrote:
> In the sql server 2005, why do I need to perform querying as followed
> "SELECT * FROM Productiion.Product"
> Why do i need to stick the prefix Production to the table named
> "product" in Adventurework sample database?
> Any idea would be appreciate.
SQL Server 2005 uses the concept of schemas. That is, objects are owned
by schemas, and not users as they have been in the past. The separation
is beneficial. See "User-Schema Separation" in the SQL 2005 BOL for more
information.
--
David Gugick
Quest Software
www.imceda.com
www.quest.com
Wednesday, March 7, 2012
Question about Active Directory
We have a product that is based on a oracle database supplied by 3rd
party. With the license we are not allowed to alter the database funny
enough.
The reports produced from this product do not fit for purpose and
obviously we couldnt alter it due to the additional cost. So we are
thinking to find alternatives by re designing reports in MS Access
using ODBC to Oracle database and give users interface where they can
enter parameter to view the reports.
Now, from my reserach I dont think you can link Active Directory to MS
Access. Is this right?
So I am thinking "reporting service" within SQL server. I am thinking
of having SQL Server as a shell (with no tables stored), use the
linked server to connect to the Oracle database, SQL server can link
with AD then finally produce a web form report.
Am I crazy? Is it possible to do so? The main thing is that whatever
solution, it NEEDS to use active directory for authentication.
Anyone has better idea? Many thanks
PeppeOn 25 Oct, 19:37, nujcha...@.googlemail.com wrote:
> We have a product that is based on a oracle database supplied by 3rd
> party. With the license we are not allowed to alter the database funny
> enough.
> The reports produced from this product do not fit for purpose and
> obviously we couldnt alter it due to the additional cost. So we are
> thinking to find alternatives by re designing reports in MS Access
> using ODBC to Oracle database and give users interface where they can
> enter parameter to view the reports.
> Now, from my reserach I dont think you can link Active Directory to MS
> Access. Is this right?
> So I am thinking "reporting service" within SQL server. I am thinking
> of having SQL Server as a shell (with no tables stored), use the
> linked server to connect to the Oracle database, SQL server can link
> with AD then finally produce a web form report.
> Am I crazy? Is it possible to do so? The main thing is that whatever
> solution, it NEEDS to use active directory for authentication.
> Anyone has better idea? Many thanks
> Peppe
anyone please help me I am stuck :(
party. With the license we are not allowed to alter the database funny
enough.
The reports produced from this product do not fit for purpose and
obviously we couldnt alter it due to the additional cost. So we are
thinking to find alternatives by re designing reports in MS Access
using ODBC to Oracle database and give users interface where they can
enter parameter to view the reports.
Now, from my reserach I dont think you can link Active Directory to MS
Access. Is this right?
So I am thinking "reporting service" within SQL server. I am thinking
of having SQL Server as a shell (with no tables stored), use the
linked server to connect to the Oracle database, SQL server can link
with AD then finally produce a web form report.
Am I crazy? Is it possible to do so? The main thing is that whatever
solution, it NEEDS to use active directory for authentication.
Anyone has better idea? Many thanks
PeppeOn 25 Oct, 19:37, nujcha...@.googlemail.com wrote:
> We have a product that is based on a oracle database supplied by 3rd
> party. With the license we are not allowed to alter the database funny
> enough.
> The reports produced from this product do not fit for purpose and
> obviously we couldnt alter it due to the additional cost. So we are
> thinking to find alternatives by re designing reports in MS Access
> using ODBC to Oracle database and give users interface where they can
> enter parameter to view the reports.
> Now, from my reserach I dont think you can link Active Directory to MS
> Access. Is this right?
> So I am thinking "reporting service" within SQL server. I am thinking
> of having SQL Server as a shell (with no tables stored), use the
> linked server to connect to the Oracle database, SQL server can link
> with AD then finally produce a web form report.
> Am I crazy? Is it possible to do so? The main thing is that whatever
> solution, it NEEDS to use active directory for authentication.
> Anyone has better idea? Many thanks
> Peppe
anyone please help me I am stuck :(
Subscribe to:
Posts (Atom)