When you use Sql Mgmt Studio to assign a report as a drill-through target for
a model entity, you can assign reports for both "Single Instance" and
"Multiple Instance". Does anyone know what this means? I had a 2+-hour
support session with a member of MS SQL Reporting team, and he didn't know
either.
cheers,
Helen
--
Helen Warn, PhD
Agile Software Inc.
www.agile-soft.comBy default when you save the file, where the datasource is connected through
RB,
If you have opened RB through some other server then you can attach where it
is for multiple instance of the servers. Basically to update on the report
server database of multiple servers is called multiple instance and single
server is called single instance.
Amarnath
"Helen Warn" wrote:
> When you use Sql Mgmt Studio to assign a report as a drill-through target for
> a model entity, you can assign reports for both "Single Instance" and
> "Multiple Instance". Does anyone know what this means? I had a 2+-hour
> support session with a member of MS SQL Reporting team, and he didn't know
> either.
> cheers,
> Helen
> --
> Helen Warn, PhD
> Agile Software Inc.
> www.agile-soft.com|||Actually that is not what it is used for. From
http://msdn2.microsoft.com/en-us/library/ms345298.aspx
(Lesson 12: Specifying Clickthrough Report Options from BOL):
"There are two clickthrough templates for each entity: a single instance
template and a multi-instance template. A single instance template is used
when the user clicks an instance of the entity. A multi-instance template is
used when the user clicks an aggregate value and multiple instances of the
entity are displayed."
I am sure that I am not the only person who fervently wishes that the
reference sectins of the documentation contained such information.
Cheers,
Helen
--
Helen Warn, PhD
Agile Software Inc.
www.agile-soft.com
"Amarnath" wrote:
> By default when you save the file, where the datasource is connected through
> RB,
> If you have opened RB through some other server then you can attach where it
> is for multiple instance of the servers. Basically to update on the report
> server database of multiple servers is called multiple instance and single
> server is called single instance.
> Amarnath
> "Helen Warn" wrote:
> > When you use Sql Mgmt Studio to assign a report as a drill-through target for
> > a model entity, you can assign reports for both "Single Instance" and
> > "Multiple Instance". Does anyone know what this means? I had a 2+-hour
> > support session with a member of MS SQL Reporting team, and he didn't know
> > either.
> >
> > cheers,
> >
> > Helen
> > --
> > Helen Warn, PhD
> > Agile Software Inc.
> > www.agile-soft.com
Showing posts with label single. Show all posts
Showing posts with label single. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
Mapping multiple elements to the same table
I have a huge 1+GB xml file that I'd like to bulk load into a single staging
table in SQL Server. The xml file has subelements that need to be loaded
into the same table as the parent element. For example:
<Customer>
<Address>
</Address>
<ContactInfo>
</ContactInfo>
</Customer>
I cannot seem to get an XSD that will load all the data into 1 table. Also
because of the size of the XML file, performing an XSLT transformation on the
file is not possible. What are my options? Is it possible to map
subelements to the same table as the containing element?
Could you map them to two different views of the same table?
Note also, that the mapping kind of expects that you give a relationship
annotation when you map parents and children. What is the error message or
behaviour that you are getting?
Best regards
Michael
"Mark Weber" <Mark Weber@.discussions.microsoft.com> wrote in message
news:14D8B400-733C-4080-8888-BD3551C6AD09@.microsoft.com...
>I have a huge 1+GB xml file that I'd like to bulk load into a single
>staging
> table in SQL Server. The xml file has subelements that need to be loaded
> into the same table as the parent element. For example:
> <Customer>
> <Address>
> </Address>
> <ContactInfo>
> </ContactInfo>
> </Customer>
> I cannot seem to get an XSD that will load all the data into 1 table.
> Also
> because of the size of the XML file, performing an XSLT transformation on
> the
> file is not possible. What are my options? Is it possible to map
> subelements to the same table as the containing element?
table in SQL Server. The xml file has subelements that need to be loaded
into the same table as the parent element. For example:
<Customer>
<Address>
</Address>
<ContactInfo>
</ContactInfo>
</Customer>
I cannot seem to get an XSD that will load all the data into 1 table. Also
because of the size of the XML file, performing an XSLT transformation on the
file is not possible. What are my options? Is it possible to map
subelements to the same table as the containing element?
Could you map them to two different views of the same table?
Note also, that the mapping kind of expects that you give a relationship
annotation when you map parents and children. What is the error message or
behaviour that you are getting?
Best regards
Michael
"Mark Weber" <Mark Weber@.discussions.microsoft.com> wrote in message
news:14D8B400-733C-4080-8888-BD3551C6AD09@.microsoft.com...
>I have a huge 1+GB xml file that I'd like to bulk load into a single
>staging
> table in SQL Server. The xml file has subelements that need to be loaded
> into the same table as the parent element. For example:
> <Customer>
> <Address>
> </Address>
> <ContactInfo>
> </ContactInfo>
> </Customer>
> I cannot seem to get an XSD that will load all the data into 1 table.
> Also
> because of the size of the XML file, performing an XSLT transformation on
> the
> file is not possible. What are my options? Is it possible to map
> subelements to the same table as the containing element?
Mapping multiple elements to the same table
I have a huge 1+GB xml file that I'd like to bulk load into a single staging
table in SQL Server. The xml file has subelements that need to be loaded
into the same table as the parent element. For example:
<Customer>
<Address>
</Address>
<ContactInfo>
</ContactInfo>
</Customer>
I cannot seem to get an XSD that will load all the data into 1 table. Also
because of the size of the XML file, performing an XSLT transformation on th
e
file is not possible. What are my options? Is it possible to map
subelements to the same table as the containing element?Could you map them to two different views of the same table?
Note also, that the mapping kind of expects that you give a relationship
annotation when you map parents and children. What is the error message or
behaviour that you are getting?
Best regards
Michael
"Mark Weber" <Mark Weber@.discussions.microsoft.com> wrote in message
news:14D8B400-733C-4080-8888-BD3551C6AD09@.microsoft.com...
>I have a huge 1+GB xml file that I'd like to bulk load into a single
>staging
> table in SQL Server. The xml file has subelements that need to be loaded
> into the same table as the parent element. For example:
> <Customer>
> <Address>
> </Address>
> <ContactInfo>
> </ContactInfo>
> </Customer>
> I cannot seem to get an XSD that will load all the data into 1 table.
> Also
> because of the size of the XML file, performing an XSLT transformation on
> the
> file is not possible. What are my options? Is it possible to map
> subelements to the same table as the containing element?sql
table in SQL Server. The xml file has subelements that need to be loaded
into the same table as the parent element. For example:
<Customer>
<Address>
</Address>
<ContactInfo>
</ContactInfo>
</Customer>
I cannot seem to get an XSD that will load all the data into 1 table. Also
because of the size of the XML file, performing an XSLT transformation on th
e
file is not possible. What are my options? Is it possible to map
subelements to the same table as the containing element?Could you map them to two different views of the same table?
Note also, that the mapping kind of expects that you give a relationship
annotation when you map parents and children. What is the error message or
behaviour that you are getting?
Best regards
Michael
"Mark Weber" <Mark Weber@.discussions.microsoft.com> wrote in message
news:14D8B400-733C-4080-8888-BD3551C6AD09@.microsoft.com...
>I have a huge 1+GB xml file that I'd like to bulk load into a single
>staging
> table in SQL Server. The xml file has subelements that need to be loaded
> into the same table as the parent element. For example:
> <Customer>
> <Address>
> </Address>
> <ContactInfo>
> </ContactInfo>
> </Customer>
> I cannot seem to get an XSD that will load all the data into 1 table.
> Also
> because of the size of the XML file, performing an XSLT transformation on
> the
> file is not possible. What are my options? Is it possible to map
> subelements to the same table as the containing element?sql
Friday, March 23, 2012
Many pubs or single pub with dynamic filters ??
Hello...
Some background: We have merge replication set up between SQL 2000 and
mobile devices running SQL Mobile. Each of our customers has a unique
customer id and currently we have a separate publication for each one...that
has a static filter such as "WHERE CustomerID = 12345". And on each device,
it subscribes to its own publication...based on the Customer ID.
What I am thinking about...in the near future, as our customer base grows,
is that we'll be faced with maintaining lots of Publications on the server -
one for each Customer ID.
So, would it be better to have a single publication that has dynamic
filters...based on the HostName property...which I'd set in code on the
device (based on the Customer ID) or keep things the way we have them now?
I am mostly concerned about replication/synchronization performance between
the server and the mobile devices...some of which use GPRS for connectivity.
I don't want to sacrifce any performance gains, if there are any, by having
lots of publications.
thanks for any thoughts.
- will
Here are the issues that you need to consider when moving to a single
publisher model:
1. Concurrency: syncing multiple subscribers at the same time is not
optimized in SQL2000, which will end up serializing the merge process. In
SQL2005, performance is greatly improved by allowing multiple subscribers to
sync at the same time.
2. Partitioning: When a subscriber with a given ID syncs, SQL2000 will scan
the publisher's articles for changes pertaining to that subscriber. This
process has its performance implications for large publication with large
number of changes. In SQL2005, this issue was also addressed by the use of
partition groups.
Regards,
Rafik
This posting is provided "AS IS" with no warranties, and confers no rights.
"dw" <dw@.discussions.microsoft.com> wrote in message
news:7730CDFB-81A8-437B-80A5-C5B0131814B9@.microsoft.com...
> Hello...
> Some background: We have merge replication set up between SQL 2000 and
> mobile devices running SQL Mobile. Each of our customers has a unique
> customer id and currently we have a separate publication for each
> one...that
> has a static filter such as "WHERE CustomerID = 12345". And on each
> device,
> it subscribes to its own publication...based on the Customer ID.
> What I am thinking about...in the near future, as our customer base
> grows,
> is that we'll be faced with maintaining lots of Publications on the
> server -
> one for each Customer ID.
> So, would it be better to have a single publication that has dynamic
> filters...based on the HostName property...which I'd set in code on the
> device (based on the Customer ID) or keep things the way we have them now?
> I am mostly concerned about replication/synchronization performance
> between
> the server and the mobile devices...some of which use GPRS for
> connectivity.
> I don't want to sacrifce any performance gains, if there are any, by
> having
> lots of publications.
> thanks for any thoughts.
> - will
|||Hi...
Thanks for the quotes from the BOL. However, we cannot move to SQL 2005 for
a while...so these won't help me now and for the near future.
Any other thoughts regarding my question...which is simply, "Is it better to
have one publication that multiple subscribers sync with...using their
Customer ID in the filtering of the data, or is it better to have multiple
publications that are unique to each subscriber?" And, when I ask which is
"better", I mean from a replication/synchronization performance aspect...from
the subscriber's end of the things.
thanks
- will
"Rafik Robeal" wrote:
> Here are the issues that you need to consider when moving to a single
> publisher model:
>
> 1. Concurrency: syncing multiple subscribers at the same time is not
> optimized in SQL2000, which will end up serializing the merge process. In
> SQL2005, performance is greatly improved by allowing multiple subscribers to
> sync at the same time.
>
> 2. Partitioning: When a subscriber with a given ID syncs, SQL2000 will scan
> the publisher's articles for changes pertaining to that subscriber. This
> process has its performance implications for large publication with large
> number of changes. In SQL2005, this issue was also addressed by the use of
> partition groups.
>
> Regards,
> Rafik
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "dw" <dw@.discussions.microsoft.com> wrote in message
> news:7730CDFB-81A8-437B-80A5-C5B0131814B9@.microsoft.com...
>
>
|||I have found that static filters perform better than dynamic ones. Obviously
however, there is more management (DBA work) to do.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks for the reply and info. That is what I was thinking...that the
performance would be better forindividual publications based on a static
filter...but figured I should toss this question out to the group, in case I
was missing something.
thanks
- will
"Paul Ibison" wrote:
> I have found that static filters perform better than dynamic ones. Obviously
> however, there is more management (DBA work) to do.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
Some background: We have merge replication set up between SQL 2000 and
mobile devices running SQL Mobile. Each of our customers has a unique
customer id and currently we have a separate publication for each one...that
has a static filter such as "WHERE CustomerID = 12345". And on each device,
it subscribes to its own publication...based on the Customer ID.
What I am thinking about...in the near future, as our customer base grows,
is that we'll be faced with maintaining lots of Publications on the server -
one for each Customer ID.
So, would it be better to have a single publication that has dynamic
filters...based on the HostName property...which I'd set in code on the
device (based on the Customer ID) or keep things the way we have them now?
I am mostly concerned about replication/synchronization performance between
the server and the mobile devices...some of which use GPRS for connectivity.
I don't want to sacrifce any performance gains, if there are any, by having
lots of publications.
thanks for any thoughts.
- will
Here are the issues that you need to consider when moving to a single
publisher model:
1. Concurrency: syncing multiple subscribers at the same time is not
optimized in SQL2000, which will end up serializing the merge process. In
SQL2005, performance is greatly improved by allowing multiple subscribers to
sync at the same time.
2. Partitioning: When a subscriber with a given ID syncs, SQL2000 will scan
the publisher's articles for changes pertaining to that subscriber. This
process has its performance implications for large publication with large
number of changes. In SQL2005, this issue was also addressed by the use of
partition groups.
Regards,
Rafik
This posting is provided "AS IS" with no warranties, and confers no rights.
"dw" <dw@.discussions.microsoft.com> wrote in message
news:7730CDFB-81A8-437B-80A5-C5B0131814B9@.microsoft.com...
> Hello...
> Some background: We have merge replication set up between SQL 2000 and
> mobile devices running SQL Mobile. Each of our customers has a unique
> customer id and currently we have a separate publication for each
> one...that
> has a static filter such as "WHERE CustomerID = 12345". And on each
> device,
> it subscribes to its own publication...based on the Customer ID.
> What I am thinking about...in the near future, as our customer base
> grows,
> is that we'll be faced with maintaining lots of Publications on the
> server -
> one for each Customer ID.
> So, would it be better to have a single publication that has dynamic
> filters...based on the HostName property...which I'd set in code on the
> device (based on the Customer ID) or keep things the way we have them now?
> I am mostly concerned about replication/synchronization performance
> between
> the server and the mobile devices...some of which use GPRS for
> connectivity.
> I don't want to sacrifce any performance gains, if there are any, by
> having
> lots of publications.
> thanks for any thoughts.
> - will
|||Hi...
Thanks for the quotes from the BOL. However, we cannot move to SQL 2005 for
a while...so these won't help me now and for the near future.
Any other thoughts regarding my question...which is simply, "Is it better to
have one publication that multiple subscribers sync with...using their
Customer ID in the filtering of the data, or is it better to have multiple
publications that are unique to each subscriber?" And, when I ask which is
"better", I mean from a replication/synchronization performance aspect...from
the subscriber's end of the things.
thanks
- will
"Rafik Robeal" wrote:
> Here are the issues that you need to consider when moving to a single
> publisher model:
>
> 1. Concurrency: syncing multiple subscribers at the same time is not
> optimized in SQL2000, which will end up serializing the merge process. In
> SQL2005, performance is greatly improved by allowing multiple subscribers to
> sync at the same time.
>
> 2. Partitioning: When a subscriber with a given ID syncs, SQL2000 will scan
> the publisher's articles for changes pertaining to that subscriber. This
> process has its performance implications for large publication with large
> number of changes. In SQL2005, this issue was also addressed by the use of
> partition groups.
>
> Regards,
> Rafik
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "dw" <dw@.discussions.microsoft.com> wrote in message
> news:7730CDFB-81A8-437B-80A5-C5B0131814B9@.microsoft.com...
>
>
|||I have found that static filters perform better than dynamic ones. Obviously
however, there is more management (DBA work) to do.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Thanks for the reply and info. That is what I was thinking...that the
performance would be better forindividual publications based on a static
filter...but figured I should toss this question out to the group, in case I
was missing something.
thanks
- will
"Paul Ibison" wrote:
> I have found that static filters perform better than dynamic ones. Obviously
> however, there is more management (DBA work) to do.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
Monday, March 19, 2012
Manual Starting SQL Server ... delay...
When I start the SQL Server by command prompt for single user mode it is
taking lots of time(15 minutes) to start the SQL Server. My computer is a
slow system but it is not very bad slow computer.
IS it a resonable time or not?
SQL 2K.
Thanks,
Smith
Therefore you should look in the SQLServer logs,how much time the databases
need to come up,on every start the database are checked while opened if any
inconsictencys exsists. If so,the database is "repaired" (open transactions
are rolled back,etc.). The betteryou leave the system duringthe shutdown the
faster it gets up on a restart.
SQL Server logs can be found in the Control node of SQL Server -- Current
Log.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Arora Smith" <Arora_Smith@.hotmail.com> schrieb im Newsbeitrag
news:%233MaZErfFHA.460@.TK2MSFTNGP09.phx.gbl...
> When I start the SQL Server by command prompt for single user mode it is
> taking lots of time(15 minutes) to start the SQL Server. My computer is a
> slow system but it is not very bad slow computer.
> IS it a resonable time or not?
> SQL 2K.
> Thanks,
> Smith
>
>
taking lots of time(15 minutes) to start the SQL Server. My computer is a
slow system but it is not very bad slow computer.
IS it a resonable time or not?
SQL 2K.
Thanks,
Smith
Therefore you should look in the SQLServer logs,how much time the databases
need to come up,on every start the database are checked while opened if any
inconsictencys exsists. If so,the database is "repaired" (open transactions
are rolled back,etc.). The betteryou leave the system duringthe shutdown the
faster it gets up on a restart.
SQL Server logs can be found in the Control node of SQL Server -- Current
Log.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Arora Smith" <Arora_Smith@.hotmail.com> schrieb im Newsbeitrag
news:%233MaZErfFHA.460@.TK2MSFTNGP09.phx.gbl...
> When I start the SQL Server by command prompt for single user mode it is
> taking lots of time(15 minutes) to start the SQL Server. My computer is a
> slow system but it is not very bad slow computer.
> IS it a resonable time or not?
> SQL 2K.
> Thanks,
> Smith
>
>
Manual Starting SQL Server ... delay...
When I start the SQL Server by command prompt for single user mode it is
taking lots of time(15 minutes) to start the SQL Server. My computer is a
slow system but it is not very bad slow computer.
IS it a resonable time or not?
SQL 2K.
Thanks,
SmithTherefore you should look in the SQLServer logs,how much time the databases
need to come up,on every start the database are checked while opened if any
inconsictencys exsists. If so,the database is "repaired" (open transactions
are rolled back,etc.). The betteryou leave the system duringthe shutdown the
faster it gets up on a restart.
SQL Server logs can be found in the Control node of SQL Server -- Current
Log.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Arora Smith" <Arora_Smith@.hotmail.com> schrieb im Newsbeitrag
news:%233MaZErfFHA.460@.TK2MSFTNGP09.phx.gbl...
> When I start the SQL Server by command prompt for single user mode it is
> taking lots of time(15 minutes) to start the SQL Server. My computer is a
> slow system but it is not very bad slow computer.
> IS it a resonable time or not?
> SQL 2K.
> Thanks,
> Smith
>
>
taking lots of time(15 minutes) to start the SQL Server. My computer is a
slow system but it is not very bad slow computer.
IS it a resonable time or not?
SQL 2K.
Thanks,
SmithTherefore you should look in the SQLServer logs,how much time the databases
need to come up,on every start the database are checked while opened if any
inconsictencys exsists. If so,the database is "repaired" (open transactions
are rolled back,etc.). The betteryou leave the system duringthe shutdown the
faster it gets up on a restart.
SQL Server logs can be found in the Control node of SQL Server -- Current
Log.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Arora Smith" <Arora_Smith@.hotmail.com> schrieb im Newsbeitrag
news:%233MaZErfFHA.460@.TK2MSFTNGP09.phx.gbl...
> When I start the SQL Server by command prompt for single user mode it is
> taking lots of time(15 minutes) to start the SQL Server. My computer is a
> slow system but it is not very bad slow computer.
> IS it a resonable time or not?
> SQL 2K.
> Thanks,
> Smith
>
>
Manual Starting SQL Server ... delay...
When I start the SQL Server by command prompt for single user mode it is
taking lots of time(15 minutes) to start the SQL Server. My computer is a
slow system but it is not very bad slow computer.
IS it a resonable time or not?
SQL 2K.
Thanks,
SmithTherefore you should look in the SQLServer logs,how much time the databases
need to come up,on every start the database are checked while opened if any
inconsictencys exsists. If so,the database is "repaired" (open transactions
are rolled back,etc.). The betteryou leave the system duringthe shutdown the
faster it gets up on a restart.
SQL Server logs can be found in the Control node of SQL Server -- Current
Log.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Arora Smith" <Arora_Smith@.hotmail.com> schrieb im Newsbeitrag
news:%233MaZErfFHA.460@.TK2MSFTNGP09.phx.gbl...
> When I start the SQL Server by command prompt for single user mode it is
> taking lots of time(15 minutes) to start the SQL Server. My computer is a
> slow system but it is not very bad slow computer.
> IS it a resonable time or not?
> SQL 2K.
> Thanks,
> Smith
>
>
taking lots of time(15 minutes) to start the SQL Server. My computer is a
slow system but it is not very bad slow computer.
IS it a resonable time or not?
SQL 2K.
Thanks,
SmithTherefore you should look in the SQLServer logs,how much time the databases
need to come up,on every start the database are checked while opened if any
inconsictencys exsists. If so,the database is "repaired" (open transactions
are rolled back,etc.). The betteryou leave the system duringthe shutdown the
faster it gets up on a restart.
SQL Server logs can be found in the Control node of SQL Server -- Current
Log.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Arora Smith" <Arora_Smith@.hotmail.com> schrieb im Newsbeitrag
news:%233MaZErfFHA.460@.TK2MSFTNGP09.phx.gbl...
> When I start the SQL Server by command prompt for single user mode it is
> taking lots of time(15 minutes) to start the SQL Server. My computer is a
> slow system but it is not very bad slow computer.
> IS it a resonable time or not?
> SQL 2K.
> Thanks,
> Smith
>
>
Subscribe to:
Posts (Atom)