Re: Accessing the underlying sql query from the rdl file

Our client uses the report builder to generate reports for collection of employees. We would like to use the employee records in this report to perform some additional processing (such as the list of employees gets assigned to a particular group).

Programmatically, I can retrieve a byte stream from rs.GetReportDefinition( "\myClientEmpReport") and deserialize the stream into Report object (as define by ReportDefinition.xsd).

I can then manually drill down and retrieve the SematicQuery xml from the commandText field.

The problem is how to convert the SemanticQuery format into a T-Sql query that I can run against the view that the report model is based off of.

Is this possible?

Thanks,

Arjay

P.S. Running SQL 2005 Reporting Services, VC# 2005, ASP.Net 2.0.

After attempting to autogenerate serialization classes on the SemanticQuery xml with Xsd and XsdObjectGen, I ended up hand coding some classes that handled recursion. From there, I was able to regenerate the sql query by walking through the filter and grouping sections. While this isn't a generic solution, it works well for my needs because the model I need this for is a single datasource derived from a view.

As a feature request, it sure would be nice to be able get the query string from the reporting engine directly.

[ODBC SQL Server Driver]Communication Link Failure

I have a third party Client (Rational Clearquest) connecting to a SQL server
with an ODBC connection. Recently a few of the developers (not all) have
started getting "[ODBC SQL Server Driver]Communication Link Failure" after 5
minutes of inactivity.
I had the a network sniff done on the SQL server as the two clients are
connecting (one that gets the message and one that doesn't). The one that
doesn't get the message was utilizing NetBios to maintain the connection
while the ones that were didn't use Netbios.
Is there something I should look at in the ODBC connection, the SQL server,
or somewhere else?
You may want to look at what protocols are being used by the
two. In the ODBC Data Source Administrator applet, select
the DSN, select configure and on the second screen, select
Client Configuration. This will show the protocol being
used.
-Sue
On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
<james_topa@.reyrey.com> wrote:

>I have a third party Client (Rational Clearquest) connecting to a SQL server
>with an ODBC connection. Recently a few of the developers (not all) have
>started getting "[ODBC SQL Server Driver]Communication Link Failure" after 5
>minutes of inactivity.
>I had the a network sniff done on the SQL server as the two clients are
>connecting (one that gets the message and one that doesn't). The one that
>doesn't get the message was utilizing NetBios to maintain the connection
>while the ones that were didn't use Netbios.
>Is there something I should look at in the ODBC connection, the SQL server,
>or somewhere else?
|||Both of clients (the one that gets the message and one that doesn't) use
TCP/IP protocol.
"Sue Hoegemeier" wrote:

> You may want to look at what protocols are being used by the
> two. In the ODBC Data Source Administrator applet, select
> the DSN, select configure and on the second screen, select
> Client Configuration. This will show the protocol being
> used.
> -Sue
> On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>
|||I'd also check in sysprocesses for their connections to
verify that they all are actually using TCP-IP. Generally
you'd see the NetBios connection with named pipes.
Not that it will necessarily resolve your issue though if
the NetBios connections are the ones that do not time out.
So they use the same application (so the same connection
strings), the same drivers, the same MDAC versions, the same
protocols, there have been no updates to the application or
the OS on the PCs and now some timeout and others do not and
the ones that do not have a Netbios connection?
Are there aliases defined on the clients or entries in the
host file the clients? Also, are there any network related
issues logged in the event logs on the clients?
-Sue
On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Both of clients (the one that gets the message and one that doesn't) use
>TCP/IP protocol.
>"Sue Hoegemeier" wrote:
|||Neither have network issues in the Event Log on their desktops
Neither have entries in Host or LMHost files
Both have MDAC 2.71.9030.4
"Sue Hoegemeier" wrote:

> I'd also check in sysprocesses for their connections to
> verify that they all are actually using TCP-IP. Generally
> you'd see the NetBios connection with named pipes.
> Not that it will necessarily resolve your issue though if
> the NetBios connections are the ones that do not time out.
> So they use the same application (so the same connection
> strings), the same drivers, the same MDAC versions, the same
> protocols, there have been no updates to the application or
> the OS on the PCs and now some timeout and others do not and
> the ones that do not have a Netbios connection?
> Are there aliases defined on the clients or entries in the
> host file the clients? Also, are there any network related
> issues logged in the event logs on the clients?
> -Sue
> On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>
|||Then I have no idea on the timeouts or the reason for
connecting differently if the PCs, apps, what they are
doing, how the are connecting and everything is exactly the
same. I'd suspect there is some difference but I have no
idea what else to suggest.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
|||Other than I'd still check sysprocesses to verify the
connection protocols being used. And things network related
like mapped drives to the server or something. But that's
all.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:

[ODBC SQL Server Driver]Communication Link Failure

I have a third party Client (Rational Clearquest) connecting to a SQL server
with an ODBC connection. Recently a few of the developers (not all) have
started getting "[ODBC SQL Server Driver]Communication Link Failure" aft
er 5
minutes of inactivity.
I had the a network sniff done on the SQL server as the two clients are
connecting (one that gets the message and one that doesn't). The one that
doesn't get the message was utilizing NetBios to maintain the connection
while the ones that were didn't use Netbios.
Is there something I should look at in the ODBC connection, the SQL server,
or somewhere else?You may want to look at what protocols are being used by the
two. In the ODBC Data Source Administrator applet, select
the DSN, select configure and on the second screen, select
Client Configuration. This will show the protocol being
used.
-Sue
On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
<james_topa@.reyrey.com> wrote:

>I have a third party Client (Rational Clearquest) connecting to a SQL serve
r
>with an ODBC connection. Recently a few of the developers (not all) have
>started getting "[ODBC SQL Server Driver]Communication Link Failure" af
ter 5
>minutes of inactivity.
>I had the a network sniff done on the SQL server as the two clients are
>connecting (one that gets the message and one that doesn't). The one that
>doesn't get the message was utilizing NetBios to maintain the connection
>while the ones that were didn't use Netbios.
>Is there something I should look at in the ODBC connection, the SQL server,
>or somewhere else?|||Both of clients (the one that gets the message and one that doesn't) use
TCP/IP protocol.
"Sue Hoegemeier" wrote:

> You may want to look at what protocols are being used by the
> two. In the ODBC Data Source Administrator applet, select
> the DSN, select configure and on the second screen, select
> Client Configuration. This will show the protocol being
> used.
> -Sue
> On Fri, 21 Jan 2005 07:15:03 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>|||I'd also check in sysprocesses for their connections to
verify that they all are actually using TCP-IP. Generally
you'd see the NetBios connection with named pipes.
Not that it will necessarily resolve your issue though if
the NetBios connections are the ones that do not time out.
So they use the same application (so the same connection
strings), the same drivers, the same MDAC versions, the same
protocols, there have been no updates to the application or
the OS on the PCs and now some timeout and others do not and
the ones that do not have a Netbios connection?
Are there aliases defined on the clients or entries in the
host file the clients? Also, are there any network related
issues logged in the event logs on the clients?
-Sue
On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Both of clients (the one that gets the message and one that doesn't) use
>TCP/IP protocol.
>"Sue Hoegemeier" wrote:
>|||Neither have network issues in the Event Log on their desktops
Neither have entries in Host or LMHost files
Both have MDAC 2.71.9030.4
"Sue Hoegemeier" wrote:

> I'd also check in sysprocesses for their connections to
> verify that they all are actually using TCP-IP. Generally
> you'd see the NetBios connection with named pipes.
> Not that it will necessarily resolve your issue though if
> the NetBios connections are the ones that do not time out.
> So they use the same application (so the same connection
> strings), the same drivers, the same MDAC versions, the same
> protocols, there have been no updates to the application or
> the OS on the PCs and now some timeout and others do not and
> the ones that do not have a Netbios connection?
> Are there aliases defined on the clients or entries in the
> host file the clients? Also, are there any network related
> issues logged in the event logs on the clients?
> -Sue
> On Thu, 27 Jan 2005 06:29:04 -0800, "topason"
> <james_topa@.reyrey.com> wrote:
>
>|||Then I have no idea on the timeouts or the reason for
connecting differently if the PCs, apps, what they are
doing, how the are connecting and everything is exactly the
same. I'd suspect there is some difference but I have no
idea what else to suggest.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
>|||Other than I'd still check sysprocesses to verify the
connection protocols being used. And things network related
like mapped drives to the server or something. But that's
all.
-Sue
On Thu, 27 Jan 2005 10:11:05 -0800, "topason"
<james_topa@.reyrey.com> wrote:
[vbcol=seagreen]
>Neither have network issues in the Event Log on their desktops
>Neither have entries in Host or LMHost files
>Both have MDAC 2.71.9030.4
>"Sue Hoegemeier" wrote:
>

[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.

I'm using JBuilder X, writing a client application and connecting to
database
SQL Server 2000 with JDBC driver.
when i have Windows Xp Pro with service Pack 1
i don't have a problem
all works
now with Windows Xp Pro and service Pack 2 i have this problem
[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
See com.borland.dx.dataset.DataSetException error code: BASE+66
com.borland.dx.dataset.DataSetException: [Microsoft][SQLServer 2000 Driver
for JDBC]Error establishing socket.
at com.borland.dx.dataset.DataSetException.a(Unknown Source)
at com.borland.dx.dataset.DataSetException.throwExcep tion(Unknown Source)
at com.borland.dx.dataset.DataSetException.SQLExcepti on(Unknown Source)
at com.borland.dx.sql.dataset.Database.openConnection (Unknown Source)
at com.borland.dx.sql.dataset.Database.createPrepared Statement(Unknown
Source)
at com.borland.dx.sql.dataset.o.a(Unknown Source)
at com.borland.dx.sql.dataset.o.d(Unknown Source)
at com.borland.dx.sql.dataset.o.f(Unknown Source)
at com.borland.dx.sql.dataset.QueryProvider.e(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideDat a(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.refresh(Unkn own Source)
at com.borland.dx.sql.dataset.QueryDataSet.refresh(Un known Source)
at com.borland.dx.sql.dataset.QueryDataSet.executeQue ry(Unknown Source)
at prog.Login.buttonControl1_actionPerformed(Login.ja va:131)
at prog.Login.buttonControl1_keyReleased(Login.java:2 07)
at prog.Login$2.keyReleased(Login.java:79)
at java.awt.AWTEventMulticaster.keyReleased(AWTEventM ulticaster.java:201)
at java.awt.Component.processKeyEvent(Component.java: 3680)
at javax.swing.JComponent.processKeyEvent(JComponent. java:2014)
at java.awt.Component.processEvent(Component.java:355 3)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.processKeyEvent(Con tainer.java:2155)
at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2135)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at
java.awt.EventDispatchThread.pumpOneEventForHierar chy
(EventDispatchThread.java:131)
at
java.awt.EventDispatchThread.pumpEventsForHierarch y
(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:85)
Chained exception:
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error
establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<in it>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnecti on.open(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplC onnection(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknow n Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager .java:517)
at java.sql.DriverManager.getConnection(DriverManager .java:177)
at com.borland.dx.sql.dataset.Database.openConnection (Unknown Source)
at com.borland.dx.sql.dataset.Database.createPrepared Statement(Unknown
Source)
at com.borland.dx.sql.dataset.o.a(Unknown Source)
at com.borland.dx.sql.dataset.o.d(Unknown Source)
at com.borland.dx.sql.dataset.o.f(Unknown Source)
at com.borland.dx.sql.dataset.QueryProvider.e(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideDat a(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.refresh(Unkn own Source)
at com.borland.dx.sql.dataset.QueryDataSet.refresh(Un known Source)
at com.borland.dx.sql.dataset.QueryDataSet.executeQue ry(Unknown Source)
at prog.Login.buttonControl1_actionPerformed(Login.ja va:131)
at prog.Login.buttonControl1_keyReleased(Login.java:2 07)
at prog.Login$2.keyReleased(Login.java:79)
at java.awt.AWTEventMulticaster.keyReleased(AWTEventM ulticaster.java:201)
at java.awt.Component.processKeyEvent(Component.java: 3680)
at javax.swing.JComponent.processKeyEvent(JComponent. java:2014)
at java.awt.Component.processEvent(Component.java:355 3)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.processKeyEvent(Con tainer.java:2155)
at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2135)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at
java.awt.EventDispatchThread.pumpOneEventForHierar chy
(EventDispatchThread.java:131)
at
java.awt.EventDispatchThread.pumpEventsForHierarch y
(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:85)
ava.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error
establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<in it>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnecti on.open(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplC onnection(Unknown
Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknow n Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager .java:517)
at java.sql.DriverManager.getConnection(DriverManager .java:177)
at com.borland.dx.sql.dataset.Database.openConnection (Unknown Source)
at com.borland.dx.sql.dataset.Database.createPrepared Statement(Unknown
Source)
at com.borland.dx.sql.dataset.o.a(Unknown Source)
at com.borland.dx.sql.dataset.o.d(Unknown Source)
at com.borland.dx.sql.dataset.o.f(Unknown Source)
at com.borland.dx.sql.dataset.QueryProvider.e(Unknown Source)
at com.borland.dx.sql.dataset.JdbcProvider.provideDat a(Unknown Source)
at com.borland.dx.dataset.StorageDataSet.refresh(Unkn own Source)
at com.borland.dx.sql.dataset.QueryDataSet.refresh(Un known Source)
at com.borland.dx.sql.dataset.QueryDataSet.executeQue ry(Unknown Source)
at prog.Login.buttonControl1_actionPerformed(Login.ja va:131)
at prog.Login.buttonControl1_keyReleased(Login.java:2 07)
at prog.Login$2.keyReleased(Login.java:79)
at java.awt.AWTEventMulticaster.keyReleased(AWTEventM ulticaster.java:201)
at java.awt.Component.processKeyEvent(Component.java: 3680)
at javax.swing.JComponent.processKeyEvent(JComponent. java:2014)
at java.awt.Component.processEvent(Component.java:355 3)
at java.awt.Container.processEvent(Container.java:116 4)
at java.awt.Component.dispatchEventImpl(Component.jav a:2593)
at java.awt.Container.dispatchEventImpl(Container.jav a:1213)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.LightweightDispatcher.processKeyEvent(Con tainer.java:2155)
at java.awt.LightweightDispatcher.dispatchEvent(Conta iner.java:2135)
at java.awt.Container.dispatchEventImpl(Container.jav a:1200)
at java.awt.Window.dispatchEventImpl(Window.java:914)
at java.awt.Component.dispatchEvent(Component.java:24 97)
at java.awt.EventQueue.dispatchEvent(EventQueue.java: 339)
at
java.awt.EventDispatchThread.pumpOneEventForHierar chy
(EventDispatchThread.java:131)
at
java.awt.EventDispatchThread.pumpEventsForHierarch y
(EventDispatchThread.java:98)
at java.awt.EventDispatchThread.pumpEvents(EventDispa tchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThre ad.java:85)
Thanks very much!
Take a look at the firewall configuration. XP SP2 comes with a firewall
that blocks all ports by default.
Alin,
The jTDS Project.
|||thanks .
the firewall want's one exeption for sql server

[INSTALL SQL SERVER] GOT A WARNING MESSAGE

[Microsoft SQL server 2000 standard edition server component is not
supported ont this operation system
Only client components will be avaiable for installation ]
my OS is winXP professional edition.
Anything wrong ?
please help
It is not possible to install SQL Server (the server edition) on to a =
desktop OS such as XP Pro. =20
You do have a few options if you need the DBMS installed on your =
computer (for example for development/testing). You can install the =
Personal Edition or the Developer Edition of SQL Server to your desktop =
machine.
--=20
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
>=20
> my OS is winXP professional edition.
> Anything wrong ?
> please help
>=20
>
|||That's mean I can install to window server2000 but not XP Pro ?
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
It is not possible to install SQL Server (the server edition) on to a
desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your computer
(for example for development/testing). You can install the Personal Edition
or the Developer Edition of SQL Server to your desktop machine.
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> my OS is winXP professional edition.
> Anything wrong ?
> please help
>
|||> That's mean I can install to window server2000 but not XP Pro ?
That is the expected (and correct) behavior.

> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
This is a true statement

> Only client components will be avaiable for installation ]
Also a true statement

> my OS is winXP professional edition.
This is your problem. The server editions (Standard and Enterprise) of =
SQL Server do not install on to desktop operating systems. If you want =
to install SQL Server onto your desktop operating system you will need =
to install the Personal Edition, the Developer Edition, or a trial =
edition.

> Anything wrong ?
You are trying to install SQL Server onto an operating system that it =
does not install on.
--=20
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =
news:%23b76DCPPEHA.3128@.TK2MSFTNGP10.phx.gbl...
> That's mean I can install to window server2000 but not XP Pro ?
>=20
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
> news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
> It is not possible to install SQL Server (the server edition) on to a
> desktop OS such as XP Pro.
>=20
> You do have a few options if you need the DBMS installed on your =
computer
> (for example for development/testing). You can install the Personal =
Edition
> or the Developer Edition of SQL Server to your desktop machine.
>=20
> --=20
> Keith
>=20
>=20
> "Agnes" <agnes@.dynamictech.com.hk> wrote in message
> news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
>=20
>

[INSTALL SQL SERVER] GOT A WARNING MESSAGE

[Microsoft SQL server 2000 standard edition server component is not
supported ont this operation system
Only client components will be avaiable for installation ]
my OS is winXP professional edition.
Anything wrong '
please helpIt is not possible to install SQL Server (the server edition) on to a =
desktop OS such as XP Pro. =20
You do have a few options if you need the DBMS installed on your =
computer (for example for development/testing). You can install the =
Personal Edition or the Developer Edition of SQL Server to your desktop =
machine.
--=20
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
>=20
> my OS is winXP professional edition.
> Anything wrong '
> please help
>=20
>|||That's mean I can install to window server2000 but not XP Pro '
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
It is not possible to install SQL Server (the server edition) on to a
desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your computer
(for example for development/testing). You can install the Personal Edition
or the Developer Edition of SQL Server to your desktop machine.
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> my OS is winXP professional edition.
> Anything wrong '
> please help
>|||> That's mean I can install to window server2000 but not XP Pro '
That is the expected (and correct) behavior.

> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
This is a true statement

> Only client components will be avaiable for installation ]
Also a true statement

> my OS is winXP professional edition.
This is your problem. The server editions (Standard and Enterprise) of =
SQL Server do not install on to desktop operating systems. If you want =
to install SQL Server onto your desktop operating system you will need =
to install the Personal Edition, the Developer Edition, or a trial =
edition.

> Anything wrong '
You are trying to install SQL Server onto an operating system that it =
does not install on.
--=20
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =
news:%23b76DCPPEHA.3128@.TK2MSFTNGP10.phx.gbl...
> That's mean I can install to window server2000 but not XP Pro '
>=20
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
> news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
> It is not possible to install SQL Server (the server edition) on to a
> desktop OS such as XP Pro.
>=20
> You do have a few options if you need the DBMS installed on your =
computer
> (for example for development/testing). You can install the Personal =
Edition
> or the Developer Edition of SQL Server to your desktop machine.
>=20
> --=20
> Keith
>=20
>=20
> "Agnes" <agnes@.dynamictech.com.hk> wrote in message
> news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
>=20
>

[INSTALL SQL SERVER] GOT A WARNING MESSAGE

[Microsoft SQL server 2000 standard edition server component is not
supported ont this operation system
Only client components will be avaiable for installation ]
my OS is winXP professional edition.
Anything wrong '
please helpIt is not possible to install SQL Server (the server edition) on to a =desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your =computer (for example for development/testing). You can install the =Personal Edition or the Developer Edition of SQL Server to your desktop =machine.
-- Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> > my OS is winXP professional edition.
> Anything wrong '
> please help
> >|||That's mean I can install to window server2000 but not XP Pro '
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
It is not possible to install SQL Server (the server edition) on to a
desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your computer
(for example for development/testing). You can install the Personal Edition
or the Developer Edition of SQL Server to your desktop machine.
--
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> my OS is winXP professional edition.
> Anything wrong '
> please help
>|||> That's mean I can install to window server2000 but not XP Pro '
That is the expected (and correct) behavior.
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
This is a true statement
> Only client components will be avaiable for installation ]
Also a true statement
> my OS is winXP professional edition.
This is your problem. The server editions (Standard and Enterprise) of =SQL Server do not install on to desktop operating systems. If you want =to install SQL Server onto your desktop operating system you will need =to install the Personal Edition, the Developer Edition, or a trial =edition.
> Anything wrong '
You are trying to install SQL Server onto an operating system that it =does not install on.
-- Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =news:%23b76DCPPEHA.3128@.TK2MSFTNGP10.phx.gbl...
> That's mean I can install to window server2000 but not XP Pro '
> > "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
> news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
> It is not possible to install SQL Server (the server edition) on to a
> desktop OS such as XP Pro.
> > You do have a few options if you need the DBMS installed on your =computer
> (for example for development/testing). You can install the Personal =Edition
> or the Developer Edition of SQL Server to your desktop machine.
> > -- > Keith
> > > "Agnes" <agnes@.dynamictech.com.hk> wrote in message
> news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> > [Microsoft SQL server 2000 standard edition server component is not
> > supported ont this operation system
> > Only client components will be avaiable for installation ]
> >
> > my OS is winXP professional edition.
> > Anything wrong '
> > please help
> >
> >
> >

@update_mode for Bidirectional Transactional Replication

Hi
I'm in the process of working out how we are going to set up
replication for a client. Quite a daunting task.
I'm think we are going to use Bidirectional Transactional Replication,
as described here:
http://support.microsoft.com/default.aspx?scid=820675
If you look at the sample you will see that they use @.update_mode =
N'sync tran' when creating the subscription. Is this necessary? I set
it up using @.update_mode = N'read only', which seemed to work fine, but
I am worried that I might be missing something.
Any comments welcome...
Thanks
Gary
that's a doc bug - it should read readonly.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Gary van der Merwe" <garyvdm@.gmail.com> wrote in message
news:1130327855.663530.282590@.o13g2000cwo.googlegr oups.com...
> Hi
> I'm in the process of working out how we are going to set up
> replication for a client. Quite a daunting task.
> I'm think we are going to use Bidirectional Transactional Replication,
> as described here:
> http://support.microsoft.com/default.aspx?scid=820675
> If you look at the sample you will see that they use @.update_mode =
> N'sync tran' when creating the subscription. Is this necessary? I set
> it up using @.update_mode = N'read only', which seemed to work fine, but
> I am worried that I might be missing something.
> Any comments welcome...
> Thanks
> Gary
>