I want to control XML Type.

Is it posible to modify xml data of XML Type by T-SQL ?

I haven't been used to CLR in procedure.but i think that it is posible to modify.

Could you tell me how to use XML data by T-SQL

Thanks for you.

It will help if you describe the modifications you want to make; include an example of the kind of XML data you would like to modify and the expected result.

I want source control for SQL Server 2000...

Hi guys'n'girls...

I currently work for a company where we develop several large ASP.NET applications which are VERY data centric. But lately we have run into a problem on our developer DB...

On the project I am working on we currenctly have approx. 10 developers working concurrently on the database. That means that we often run into errors caused by two developers working on the same stored procedure, function or trigger so the developer who adds his changes last, overwrites the modifications done by the other developer. The obvious answer is source control for the db, but as far as I can tell this is only available for stored procedures and not for functions or triggers... And even the stored procedure solution isn't very safe because it only works if every developer is editing the procedures through VS.

So what do we do? There must be some solution to this problem... And I'm pretty convinced that we are not the first company to face this problem. Are we doing it the wrong way or do you know another solution?

Thanks in advance!

Try these two urls for options but the manual way to do it is to leave the DDL coding to one or two developers working together and run a stored proc to eliminate duplicates. Hope this helps.

http://www.allisonfamily.org/bill/library/articles/vss-sql-howto/

http://www.sqlservercentral.com/products/bwunder/archiveutility/

I thing DB2 can do it

I know that DB2 has something called the “Query Patroller” that can be useed
to proactively and dynamically control the flow of queries against your DB2
database in the following key ways:
a. Define separate query classes for queries of different sizes to better
share system resources among queries and to prevent smaller queries from
getting stuck behind larger ones
b. Give queries submitted by certain users high priority so that these
queries run sooner
c. Automatically put large queries on hold so that they can be cancelled or
scheduled to run during off-peak hours
d. Track and cancel runaway queries
The purpose of this is to allow you to regulate your database's query
workload so that small queries and high-priority queries can run promptly and
your system resources are used efficiently.
I don’t thing these thing are unreasonable requirements for a database
server in the enterprise. I’m surprised the this seems so hard to do on Sql
server.
Have anyone looked into the features on the Sql server 2005? Any
improvements there?
Are there any of you guys that has been struggling with the same problems –
and found a solution or a workaround?
"pehuan" wrote:

> When you run a process on you Windows machine, you can set the process
> priority to 'low', if you don't want the process to take resources away form
> other processes running in the same timeframe.
> Does anyone know of a similar technique for long running queries on Sql
> server 2000 or 2005?
> I have a series on long running analytical queries, where the query
> execution time is not important, and I don’t want them to take any resources
> away form other queries running in the same timeframe.
> I would like a way to tell the Sql server – “run this, but if anything else
> happens, give that the first priority!”
> Any suggestions?
>
>
Read up this article
http://www.databasejournal.com/featu...le.php/3427581
"pehuan" <pehuan@.discussions.microsoft.com> wrote in message
news:66FFBDA0-98CA-44F3-A4ED-A3B43958C546@.microsoft.com...
> I know that DB2 has something called the Query Patroller that can be
useed
> to proactively and dynamically control the flow of queries against your
DB2
> database in the following key ways:
> a. Define separate query classes for queries of different sizes to better
> share system resources among queries and to prevent smaller queries from
> getting stuck behind larger ones
> b. Give queries submitted by certain users high priority so that these
> queries run sooner
> c. Automatically put large queries on hold so that they can be cancelled
or
> scheduled to run during off-peak hours
> d. Track and cancel runaway queries
> The purpose of this is to allow you to regulate your database's query
> workload so that small queries and high-priority queries can run promptly
and
> your system resources are used efficiently.
> I dont thing these thing are unreasonable requirements for a database
> server in the enterprise. Im surprised the this seems so hard to do on
Sql
> server.
> Have anyone looked into the features on the Sql server 2005? Any
> improvements there?
> Are there any of you guys that has been struggling with the same
problems [vbcol=seagreen]
> and found a solution or a workaround?
>
> "pehuan" wrote:
form[vbcol=seagreen]
resources[vbcol=seagreen]
else[vbcol=seagreen]

I thing DB2 can do it

I know that DB2 has something called the “Query Patroller” that can be u
seed
to proactively and dynamically control the flow of queries against your DB2
database in the following key ways:
a. Define separate query classes for queries of different sizes to better
share system resources among queries and to prevent smaller queries from
getting stuck behind larger ones
b. Give queries submitted by certain users high priority so that these
queries run sooner
c. Automatically put large queries on hold so that they can be cancelled or
scheduled to run during off-peak hours
d. Track and cancel runaway queries
The purpose of this is to allow you to regulate your database's query
workload so that small queries and high-priority queries can run promptly an
d
your system resources are used efficiently.
I don’t thing these thing are unreasonable requirements for a database
server in the enterprise. I’m surprised the this seems so hard to do on Sq
l
server.
Have anyone looked into the features on the Sql server 2005? Any
improvements there?
Are there any of you guys that has been struggling with the same problems
and found a solution or a workaround?
"pehuan" wrote:

> When you run a process on you Windows machine, you can set the process
> priority to 'low', if you don't want the process to take resources away fo
rm
> other processes running in the same timeframe.
> Does anyone know of a similar technique for long running queries on Sql
> server 2000 or 2005?
> I have a series on long running analytical queries, where the query
> execution time is not important, and I don’t want them to take any resou
rces
> away form other queries running in the same timeframe.
> I would like a way to tell the Sql server – “run this, but if anything
else
> happens, give that the first priority!”
> Any suggestions?
>
>Read up this article
http://www.databasejournal.com/feat...cle.php/3427581
"pehuan" <pehuan@.discussions.microsoft.com> wrote in message
news:66FFBDA0-98CA-44F3-A4ED-A3B43958C546@.microsoft.com...
> I know that DB2 has something called the Query Patroller that can be
useed
> to proactively and dynamically control the flow of queries against your
DB2
> database in the following key ways:
> a. Define separate query classes for queries of different sizes to better
> share system resources among queries and to prevent smaller queries from
> getting stuck behind larger ones
> b. Give queries submitted by certain users high priority so that these
> queries run sooner
> c. Automatically put large queries on hold so that they can be cancelled
or
> scheduled to run during off-peak hours
> d. Track and cancel runaway queries
> The purpose of this is to allow you to regulate your database's query
> workload so that small queries and high-priority queries can run promptly
and
> your system resources are used efficiently.
> I dont thing these thing are unreasonable requirements for a database
> server in the enterprise. Im surprised the this seems so hard to do on
Sql
> server.
> Have anyone looked into the features on the Sql server 2005? Any
> improvements there?
> Are there any of you guys that has been struggling with the same
problems [vbcol=seagreen]
> and found a solution or a workaround?
>
> "pehuan" wrote:
>
form[vbcol=seagreen]
resources[vbcol=seagreen]
else[vbcol=seagreen]

I swear I saw, but exists no more

I have all the installed Control Flow Tasks. At one time I did create a Execute T-SQL Statement task, but after a couple of days when I revisited the project it is still there on my design area, but has disappeared from the Control Flow Tasks group in the toolbox. I did a check of all items. It has disappeared. Any clue(s)? I have posted a screen shot in my blog.

Jay

http://hodentek.blogspot.com/2007/08/strange-behaviour-visual-studio-2005.html

That's because the T-SQL task is under the Maintenance Plan Tasks, not Control Flow Items.

The Execute SQL Task under the Control Flow items, though, is a much better fit long term and will do the same thing as the Execute T-SQL Task.|||

Right you are. Need changing my glasses.

Jay