I had a question regarding using XML as a database rather than a data format.
Can some/all types of integrity constraints that we (can) have in a SQL database be represented/mapped to XML?
Could anyone explain or give some pointers to this...
-Aayush
I'm not sure exactly what you're asking. In general, XML isn't a database
so using it as a database doesn't make sense. In the limited scope of the
topic of this newsgroups, SQL Server 2000 and SQLXML allow you to store the
data in an XML document as one or more rows of normal relational data.
Because the XML is mapped to relational data, the integrity constraint on
the relation data apply so for example you may not be able to insert a
document that has order lines if no corresponding order header exists. Note
that this is possible because XML is being shredded into relational data and
is not an inherent part of XML. In general, XML schemas don't support
defining or enforcing most integrity constraints.
Does this answer your question?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Aayush Puri" <anonymous@.discussions.microsoft.com> wrote in message
news:3EC02BEB-4AEA-438C-AB11-4D4F33C1CD6D@.microsoft.com...
>I had a question regarding using XML as a database rather than a data
>format.
> Can some/all types of integrity constraints that we (can) have in a SQL
> database be represented/mapped to XML?
> Could anyone explain or give some pointers to this...
>
> -Aayush
>
|||Hey,
Thankx for the reply. Yeah I know that it makes little sense to use XML as
a database rather than a data format...but the app. which I am trying to
design is for users *not* having any SQL database. I was just just wondering
if XSD allows me to specify constraints alike SQL or if possible things like
triggers etc...
U got my point right.
Thankx,
-Aayush
Showing posts with label xml. Show all posts
Showing posts with label xml. Show all posts
Friday, March 9, 2012
Friday, February 24, 2012
Integration Services Configuration on Cluster
I've followed the books online help to configure SSIS (move the
MsDtsSrvr.ini.xml file, edit the file to have the correct path virtual server
name, and change the registry), restart all services...and nothing. I can
connect to SSIS fine through Management Studio, but when I click on Stored
Packages -> MSDB it hangs and eventually times out with this error message:
"The SQL Server specified in SSIS service configuration is not present or is
not available. This might occur when there is no default instance of SQL
Server."
I have a no default instance of SQL 05 on a failover cluster.
Also, I've tried every possible combination on the Server section of the
MsDtsSrvr.ini.xml file: server name\instance name, cluster name-.
Is it a dash or a backslash, I've seen different advice in articles, also.
thanks!Perhaps the configuration file isn't on the shared disk and available to
both nodes?
Please check out this article:
http://msdn2.microsoft.com/en-us/library/ms345193.aspx for complete details
of the required configuration.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
MsDtsSrvr.ini.xml file, edit the file to have the correct path virtual server
name, and change the registry), restart all services...and nothing. I can
connect to SSIS fine through Management Studio, but when I click on Stored
Packages -> MSDB it hangs and eventually times out with this error message:
"The SQL Server specified in SSIS service configuration is not present or is
not available. This might occur when there is no default instance of SQL
Server."
I have a no default instance of SQL 05 on a failover cluster.
Also, I've tried every possible combination on the Server section of the
MsDtsSrvr.ini.xml file: server name\instance name, cluster name-.
Is it a dash or a backslash, I've seen different advice in articles, also.
thanks!Perhaps the configuration file isn't on the shared disk and available to
both nodes?
Please check out this article:
http://msdn2.microsoft.com/en-us/library/ms345193.aspx for complete details
of the required configuration.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Integration Services Configuration on Cluster
I've followed the books online help to configure SSIS (move the
MsDtsSrvr.ini.xml file, edit the file to have the correct path virtual serve
r
name, and change the registry), restart all services...and nothing. I can
connect to SSIS fine through Management Studio, but when I click on Stored
Packages -> MSDB it hangs and eventually times out with this error message:
"The SQL Server specified in SSIS service configuration is not present or is
not available. This might occur when there is no default instance of SQL
Server."
I have a no default instance of SQL 05 on a failover cluster.
Also, I've tried every possible combination on the Server section of the
MsDtsSrvr.ini.xml file: server name\instance name, cluster name-.
Is it a dash or a backslash, I've seen different advice in articles, also.
thanks!Perhaps the configuration file isn't on the shared disk and available to
both nodes?
Please check out this article:
http://msdn2.microsoft.com/en-us/library/ms345193.aspx for complete details
of the required configuration.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
MsDtsSrvr.ini.xml file, edit the file to have the correct path virtual serve
r
name, and change the registry), restart all services...and nothing. I can
connect to SSIS fine through Management Studio, but when I click on Stored
Packages -> MSDB it hangs and eventually times out with this error message:
"The SQL Server specified in SSIS service configuration is not present or is
not available. This might occur when there is no default instance of SQL
Server."
I have a no default instance of SQL 05 on a failover cluster.
Also, I've tried every possible combination on the Server section of the
MsDtsSrvr.ini.xml file: server name\instance name, cluster name-.
Is it a dash or a backslash, I've seen different advice in articles, also.
thanks!Perhaps the configuration file isn't on the shared disk and available to
both nodes?
Please check out this article:
http://msdn2.microsoft.com/en-us/library/ms345193.aspx for complete details
of the required configuration.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Subscribe to:
Posts (Atom)