Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 SQL Server 2000

Author  Topic 

Greenwhite
Starting Member

5 Posts

Posted - 2010-07-05 : 21:49:31
I’m using SQL Server 2000. I need to know if any of my databases are use triggers with “OUTPUT INTO”. 1) How do I find out? 2) How do I find out if “merge” is the name of any table or column in my SQL Server 2000 databases?

3) How do I find out if I’m using XML in my SQL Server 2000 databases? I’m concerned that when I do an upgrade from 2000 to 2008, some of Microsoft’s concerns about XML Showplan and XML semantics validation will be an issue. But the databases I have aren’t overly complex. There may be no XML in them.

pk_bohra
Master Smack Fu Yak Hacker

1182 Posts

Posted - 2010-07-05 : 23:35:24
1) How do I find out?
As far as i know "OUTPUT INTO" statement is not supported in sql 2000.

2)How do I find out if “merge” is the name of any table or column in my SQL Server 2000 databases?
Query the Sysobjects and syscolumns table.

Ex: Select * from sysobjects where name ='merge' and xtype ='U'
--If you get output then its table.

Ex: Select object_name(id) as TableName,Name as ColName from syscolumns where name ='merge'
--If you get output then its column.


3) How do I find out if I’m using XML in my SQL Server 2000 databases ?
You mean whether output is generated in XML format?


Regards,
Bohra

I am here to learn from Masters and help new bees in learning.
Go to Top of Page

Greenwhite
Starting Member

5 Posts

Posted - 2010-07-06 : 01:45:44
No, the gist of my concern is that XML Showplan and XML semantics validation are vastly different in 2008 compared to previous versions. I'm not concerned if the SQL Server 2000 databases produce output in XML format. I'm concerned if the databases have XML objects or XML files. I understand the features "XML Showplan" and "XML semantics validation" could raise a problem in SQL Server 2008. Any way to address these two concerns?
Go to Top of Page
   

- Advertisement -