Multi row key updates?

I have been using MS Viso (the one that integrates with Visual Studio .NET)
to generate ddl script for my database. It uses the following update trigger
code to enforce the referential integrity, but will only execute the code fo
r
one row updates, it will throw an error for multi-row updates. I am wonderin
g
why it only allows the one row, as it appears (to me) that the code will wor
k
fine for multi-row updates as well.
UPDATE "ReferedTable"
SET "ReferedTable"."ReferedKey" = inserted."PrimaryKey"
FROM inserted, deleted, "ReferedTable"
WHERE "ReferedTable"."ReferedKey" = deleted."PrimaryKey"
I understand that it is updating the refered key column in the related
tables whenever the primary key column of the parent table is changed, but I
do not understand why it only allows one row at a time to be updated.
Can someone please explain this for me? And can it actually be used for
multi-row updates? If not then what would be a good way of doing it? Thanks--BEGIN PGP SIGNED MESSAGE--
Hash: SHA1
Why not dispense w/ the trigger and use the ON UPDATE CASCADE and ON
DELETE CASCADE methods of a Foreign Key? E.g.:
create table t (
a char(1) primary key,
c char(2) not null
)
create table s (
a char(1) not null references t (a)
on update cascade on delete cascade,
d datetime not null
)
Whenever t.a is changed s.a will reflect the changes and all rows in s.a
will be updated.
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)
--BEGIN PGP SIGNATURE--
Version: PGP for Personal Privacy 5.0
Charset: noconv
iQA/ AwUBQj4zo4echKqOuFEgEQKRgACg3GMmYjF9+Igx
UGwWwRMF3YJL5msAn0Le
4XoP+70vYIkNaJh/nfxGf6Nj
=Wx8M
--END PGP SIGNATURE--
Gary K wrote:
> I have been using MS Viso (the one that integrates with Visual Studio .NET
)
> to generate ddl script for my database. It uses the following update trigg
er
> code to enforce the referential integrity, but will only execute the code
for
> one row updates, it will throw an error for multi-row updates. I am wonder
ing
> why it only allows the one row, as it appears (to me) that the code will w
ork
> fine for multi-row updates as well.
> UPDATE "ReferedTable"
> SET "ReferedTable"."ReferedKey" = inserted."PrimaryKey"
> FROM inserted, deleted, "ReferedTable"
> WHERE "ReferedTable"."ReferedKey" = deleted."PrimaryKey"
> I understand that it is updating the refered key column in the related
> tables whenever the primary key column of the parent table is changed, but
I
> do not understand why it only allows one row at a time to be updated.
> Can someone please explain this for me? And can it actually be used for
> multi-row updates? If not then what would be a good way of doing it? Thanks[/color
]|||"MGFoster" wrote:

> Why not dispense w/ the trigger and use the ON UPDATE CASCADE and ON
> DELETE CASCADE methods of a Foreign Key? E.g.:
>
Mainly because SQL Server does not have ON UPDATE/DELETE RESTRICTED/SET
NULL/SET DEFAULT options. Also our database requirements specify before/afte
r
auditing which can only be done in INSTEAD OF triggers (due to the nature of
the tables used, which can't be changed, or at least not by me), and using
INSTEAD OF triggers precludes the use of UPDATE/DELETE foreign key
restrictions.
We have borrowed from the programming structure that Viso produces, in that
while we still create foreign key references they are disabled so we can
implement our own version of referential integrity + auditing.
Personally I would prefer to use another DB package, but unfortunately to
keep things cheap and easily integratable with our MS Office products we are
stuck with SQL Server.
Thanks for the reply MG, but sorry, it's not something we can use.|||Gary K wrote:
> "MGFoster" wrote:
>
> Mainly because SQL Server does not have ON UPDATE/DELETE RESTRICTED/SET
> NULL/SET DEFAULT options. Also our database requirements specify before/af
ter
> auditing which can only be done in INSTEAD OF triggers (due to the nature
of
> the tables used, which can't be changed, or at least not by me), and using
> INSTEAD OF triggers precludes the use of UPDATE/DELETE foreign key
> restrictions.
> We have borrowed from the programming structure that Viso produces, in tha
t
> while we still create foreign key references they are disabled so we can
> implement our own version of referential integrity + auditing.
> Personally I would prefer to use another DB package, but unfortunately to
> keep things cheap and easily integratable with our MS Office products we a
re
> stuck with SQL Server.
> Thanks for the reply MG, but sorry, it's not something we can use.
--BEGIN PGP SIGNED MESSAGE--
Hash: SHA1
Is the Primary Key (PK) an Identity column? From BOL (Instead of Update
trigger):
"Usually, when an UPDATE statement that references a table attempts to
set the value of a computed, *identity*, or timestamp column, an error
is generated because the values for these columns must be determined by
Microsoft? SQL Server?. These columns must be included in the UPDATE
statement to meet the NOT NULL requirement of the column. However, if
the UPDATE statement references a view with an INSTEAD OF UPDATE
trigger, the logic defined in the trigger can bypass these columns and
avoid the error."
HTH,
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)
--BEGIN PGP SIGNATURE--
Version: PGP for Personal Privacy 5.0
Charset: noconv
iQA/AwUBQj5HZIechKqOuFEgEQJWDACePu5W/oh+PLuf3ysomu6DVtaT6IQAoLBB
y1D1g1dzEYdEoG6vh1+WNsx1
=IYDc
--END PGP SIGNATURE--|||"MGFoster" wrote:

> Is the Primary Key (PK) an Identity column? From BOL (Instead of Update
> trigger):
> "Usually, when an UPDATE statement that references a table attempts to
> set the value of a computed, *identity*, or timestamp column, an error
> is generated because the values for these columns must be determined by
> Microsoft? SQL Server?. These columns must be included in the UPDATE
> statement to meet the NOT NULL requirement of the column. However, if
> the UPDATE statement references a view with an INSTEAD OF UPDATE
> trigger, the logic defined in the trigger can bypass these columns and
> avoid the error."
>
Nope, I try to avoid those like the plague now. We use uniqueidentifiers as
ROWGUIDCOL columns, not only for 'bookmark' uses of such a column, but also
to make replication a lot easier.
The main point of my question was to confirm that the given code would
handle multi-row referential updates on a parent table primary key column
(which i have now done in a practical experiment), and to find out why the M
S
Viso designers would only let one row be updated at a time with the code.
I have confirmed that the code will perform multi-row updates and it appears
to work correctly, but as the famous quotes says, "Just because we can do
something, does it mean we SHOULD?" I am basically looking for any problems
that might arise from the use of the code.|||I should have included this in the last message, but here is the code I used
to test the multi-row update code.
use tempdb
go
-- these table testers are only so I can reuse the code if it needed any
changes (it did)
if objectproperty(object_id('tblb'), 'IsTable')=1
drop table tblb
go
if objectproperty(object_id('tbla'), 'IsTable')=1
drop table tbla
go
create table tbla ( -- our parent table in the relationship
-- (i couldn't be bothered typing in GUIDs so we use a tinyint pk)
ii tinyint NOT NULL PRIMARY KEY,
ll varchar(50) NULL
)
go
create table tblb ( -- our child table in the relationship
ii tinyint NOT NULL PRIMARY KEY,
ll varchar(50) NULL,
ia tinyint NOT NULL,
-- and this is our relationship contraint
CONSTRAINT FK_b FOREIGN KEY (ia) REFERENCES tbla (ii)
)
go
-- we are going to look after the integrity, so we disable the constraint
alter table tblb nocheck constraint FK_b
go
create trigger tbla_upd on tbla for update as
begin
-- our test trigger is only for the update condition, and since we control
what is
-- going to happen we can skip all the extra code we will be using.
-- this code will only be executed (for every child table) when the primary
key is updated
update tblb
set tblb.ia = inserted.ii
from inserted, deleted, tblb
where tblb.ia = deleted.ii
end
go
-- insert parent table values
insert tbla values (1, 'first')
insert tbla values (2, 'second')
insert tbla values (3, 'third')
-- insert child table values
insert tblb values (1, 'first/first', 1)
insert tblb values (2, 'first/second', 2)
insert tblb values (3, 'first/third', 3)
insert tblb values (4, 'second/third', 3)
insert tblb values (5, 'second/second', 2)
insert tblb values (6, 'third/second', 2)
insert tblb values (7, 'second/first', 1)
insert tblb values (8, 'third/third', 3)
go
-- what it looks like before we change things
select * from tbla a inner join tblb b on b.ia=a.ii order by a.ll, b.ll
go
-- now we change the pk of the 'second' series to a new unique value
update tbla set ii=4 where ii=2
go
-- and we see what we get (works ok!)
select * from tbla a inner join tblb b on b.ia=a.ii order by a.ll, b.ll
go
-- now we change the pk of the 'third' series to a value that is already in
use
-- (error testing, and yes it does throw an error as it is supposed to)
update tbla set ii=4 where ii=3
go
-- and then we see what we get after the change (which doesn't happen)
select * from tbla a inner join tblb b on b.ia=a.ii order by a.ll, b.ll
go|||Gary,
The code looks wrong to me, but even so, it can't be
fixed unless there is another candidate key on the table.
First off, there is no join condition between inserted and
either of the other two tables. If 10 rows are updated, which
of the 10 inserted.PrimaryKey values will be assigned to
ReferedTable.ReferedKey? The way this proprietary
SQL Server syntax works, an arbitrary one of the 10
possibilities will be used.
But the problem is worse than that. Because the primary
key is being updated, there is no way to identify the correct
correspondence between an old row and a new row.
Suppose the update was this:
update T set
PrimaryKey =
case PrimaryKey
when 1 then 123
when 2 then 456
end
where PrimaryKey in (1,2)
Within the trigger, there is no way to distinguish
this update from a different one:
update T set
PrimaryKey =
case PrimaryKey
when 1 then 456
when 2 then 123
end
where PrimaryKey in (1,2)
At least not without it being possible to identify which
row is which on the basis of some column or columns
other than the PrimaryKey column.
If only one row is updated, the is no ambiguity.
Steve Kass
Drew University
Gary K wrote:

>I have been using MS Viso (the one that integrates with Visual Studio .NET)
>to generate ddl script for my database. It uses the following update trigge
r
>code to enforce the referential integrity, but will only execute the code f
or
>one row updates, it will throw an error for multi-row updates. I am wonderi
ng
>why it only allows the one row, as it appears (to me) that the code will wo
rk
>fine for multi-row updates as well.
>UPDATE "ReferedTable"
>SET "ReferedTable"."ReferedKey" = inserted."PrimaryKey"
>FROM inserted, deleted, "ReferedTable"
>WHERE "ReferedTable"."ReferedKey" = deleted."PrimaryKey"
>I understand that it is updating the refered key column in the related
>tables whenever the primary key column of the parent table is changed, but
I
>do not understand why it only allows one row at a time to be updated.
>Can someone please explain this for me? And can it actually be used for
>multi-row updates? If not then what would be a good way of doing it? Thanks
>|||Gary,
Check Itzik Ben-Gan's presentation & scripts on RI in SQL 7.0 and 2000 at
http://www.sql.co.il/ug/13/Thirteenth.htm.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Gary K" <GaryK@.discussions.microsoft.com> wrote in message
news:D3D0B4F4-EC82-41E6-A527-E6202A5394F7@.microsoft.com...
> I have been using MS Viso (the one that integrates with Visual Studio
.NET)
> to generate ddl script for my database. It uses the following update
trigger
> code to enforce the referential integrity, but will only execute the code
for
> one row updates, it will throw an error for multi-row updates. I am
wondering
> why it only allows the one row, as it appears (to me) that the code will
work
> fine for multi-row updates as well.
> UPDATE "ReferedTable"
> SET "ReferedTable"."ReferedKey" = inserted."PrimaryKey"
> FROM inserted, deleted, "ReferedTable"
> WHERE "ReferedTable"."ReferedKey" = deleted."PrimaryKey"
> I understand that it is updating the refered key column in the related
> tables whenever the primary key column of the parent table is changed, but
I
> do not understand why it only allows one row at a time to be updated.
> Can someone please explain this for me? And can it actually be used for
> multi-row updates? If not then what would be a good way of doing it?
Thanks

Mulitple Update in mYSQL

I need to write a query to update two mysql tables simultaneously ie:
i have two tables:
Table1 and Table2.
and each of the these tables have a realting field... So i tried writing a update query this way.

Update TABLE1,TABLE2 SET TABLE1.field1 = 'aaaa' , TABLE2.field1='bbb' Where TABLE1.field2 = 12 and TABLE1.field1=TABLE2.field1

But this query showed me an error.. i can do this breaking into 2 queries, but i want it to be done in one single go... any idea on this??

Thanking you in advance..Originally posted by nikks525
I need to write a query to update two mysql tables simultaneously ie:
i have two tables:
Table1 and Table2.
and each of the these tables have a realting field... So i tried writing a update query this way.

Update TABLE1,TABLE2 SET TABLE1.field1 = 'aaaa' , TABLE2.field1='bbb' Where TABLE1.field2 = 12 and TABLE1.field1=TABLE2.field1

But this query showed me an error.. i can do this breaking into 2 queries, but i want it to be done in one single go... any idea on this??

Thanking you in advance..
I don't use MySQL but updating 2 tables in one statement is not allowed generally in SQL. One way to achieve something like it (in Oracle at least) is to create a view for the join query with an INSTEAD OF UPDATE trigger. So the user can update one view, and the trigger actually updates 2 tables. I don't know if MySQL supports INSTEAD OF triggers, though.

Why do you want to do it anyway? Is it just a covenience issue or do you have some other reason for not wanting to perform 2 updates?|||I just noticed this before replying to the same thread in the MySQL forum. Simple answer; to the best of my knowledge, you can't. It's not valid SQL. And to extend my learned chum andrewst's comments, MySQL doesn't support triggers or views so no go there I'm afraid.

I'm also intrigued as to why you need to do this?|||I just wanted to do a easy job with writing the update in a single query.. rather than 2 different queries..
yea i think it needs to be broken up into 2 different Queries ..

anyway thanks for your replies ..|||Originally posted by andrewst
I don't use MySQL but updating 2 tables in one statement is not allowed generally in SQL. One way to achieve something like it (in Oracle at least) is to create a view for the join query with an INSTEAD OF UPDATE trigger. So the user can update one view, and the trigger actually updates 2 tables. I don't know if MySQL supports INSTEAD OF triggers, though.

Why do you want to do it anyway? Is it just a covenience issue or do you have some other reason for not wanting to perform 2 updates?

CAN U PLEASE LET ME KNOW HOW TO CREATE VIEWS IN MYSQL TO UPDATE 2 TABLES IN MYSQL|||No need to shout :p

It's been a while since I checked up with developments over at MySQL AB but (see my post above) as far as I know, you can't. No triggers, no updateable views and transaction support only in certain table types.

Why can't you fire off two update statements?

(caveat: I'm quite happy to have my comments above proven wrong by someone more up-to-date on the latest MySQL releases)

MSXML6.CAB

Hi,

I am currently using msxml4.dll as part of my web application, but my project manager requested that I update to MSXML6. That makes sense, but I cannot find a corresponding msxml6.cab file that I can download and distribute. The only thing that I web search turned up is MSXML6 SP1 MSI, which does not help web installations and cross operating system compatibility.

1. Is there an msxml6.cab? If so how can I get it?

2. Is it legal to redistribute msxml6.cab, if it exists? If not, can I redistribute msxml4.cab?

Thanks in advance,

Sarah M. Weinberger
ButterflyVista
http://www.butterflyvista.com/

Don′t know if that is still valid, but did you see the Blog from the XMLTeam of MS ?

http://blogs.msdn.com/xmlteam/archive/2006/10/23/using-the-right-version-of-msxml-in-internet-explorer.aspx

"Hi Andrew, right now we don't support CAB installation for MSXML6. But we've heard from a bunch of folks now that this is an important scenario so we're looking at wrapping our existing installer. "

Maybe you can come along with the MSI package and can create a boostrapper ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

MSSRS 2000 Restarts Windows XP system after the latest update

Hi Microsoft Sql server reproting services restarts the windows xp installed
desktops when we try to print using the print oprion in the report.
This is happening for lot of my clients.
How to fix this. This is happening only after the latest update in March.
My company has aroung 40,000 people who will be using the reports generated
by the reporting services most of them have windows xp with autometic update
switched on. Hence once the update happnes when they want to take a print out
of a report which shown using the MSSRS 2000 in internet explorere and
clicked onthe print icon in the report window system gets restarted.
Please help
Thanking you
SureshSuresh,
The first time you click the print icon a ActiveX control is installed. You
must have some sort of common desktop configuration that is blowing up when
you try to install this ActiveX.
First thing I would do is look at IE's security settings surrounding the
ActiveX downloading/installing.
--
Andy Potter
blog : http://sqlreportingservices.spaces.live.com
info@.(NOSPAM)lakeclaireenterprises.com
"Suresh" <Suresh@.discussions.microsoft.com> wrote in message
news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> Hi Microsoft Sql server reproting services restarts the windows xp
> installed
> desktops when we try to print using the print oprion in the report.
> This is happening for lot of my clients.
> How to fix this. This is happening only after the latest update in March.
> My company has aroung 40,000 people who will be using the reports
> generated
> by the reporting services most of them have windows xp with autometic
> update
> switched on. Hence once the update happnes when they want to take a print
> out
> of a report which shown using the MSSRS 2000 in internet explorere and
> clicked onthe print icon in the report window system gets restarted.
> Please help
> Thanking you
> Suresh
>|||Thanks Andy.
But the issue is not with installing the active x.
In many systems the active x was installed long before.
It was working fine until recently a windws xp update was released.
After the update only when clicked on the print icon in the report displayed
in desktops the systems get restarted.
So this should be a bug introduced due to the recent update by Microsft
update for windows Xp. I am looking for a patch for this.
Regards
Suresh
"Andy Potter" wrote:
> Suresh,
> The first time you click the print icon a ActiveX control is installed. You
> must have some sort of common desktop configuration that is blowing up when
> you try to install this ActiveX.
> First thing I would do is look at IE's security settings surrounding the
> ActiveX downloading/installing.
> --
> Andy Potter
> blog : http://sqlreportingservices.spaces.live.com
> info@.(NOSPAM)lakeclaireenterprises.com
> "Suresh" <Suresh@.discussions.microsoft.com> wrote in message
> news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> > Hi Microsoft Sql server reproting services restarts the windows xp
> > installed
> > desktops when we try to print using the print oprion in the report.
> >
> > This is happening for lot of my clients.
> > How to fix this. This is happening only after the latest update in March.
> >
> > My company has aroung 40,000 people who will be using the reports
> > generated
> > by the reporting services most of them have windows xp with autometic
> > update
> > switched on. Hence once the update happnes when they want to take a print
> > out
> > of a report which shown using the MSSRS 2000 in internet explorere and
> > clicked onthe print icon in the report window system gets restarted.
> >
> > Please help
> > Thanking you
> > Suresh
> >
> >
>
>|||Suresh,
We are facing the same problem..
I was searching around when i got something on this issue in the below
URL.
Not sure to what extent it will identify and solve this problem, but
may be worth a read.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1480005&SiteID=1
Please let us know if any body gets some solution to this
On Apr 17, 4:08 pm, Suresh <Sur...@.discussions.microsoft.com> wrote:
> Thanks Andy.
> But the issue is not with installing the active x.
> In many systems the active x was installed long before.
> It was working fine until recently a windws xp update was released.
> After the update only when clicked on theprinticon in the report displayed
> in desktops the systems get restarted.
> So this should be a bug introduced due to the recent update by Microsft
> update for windows Xp. I am looking for a patch for this.
> Regards
> Suresh
>
> "Andy Potter" wrote:
> > Suresh,
> > The first time you click theprinticon a ActiveX control is installed. You
> > must have some sort of common desktop configuration that is blowing up when
> > you try to install this ActiveX.
> > First thing I would do is look at IE's security settings surrounding the
> > ActiveX downloading/installing.
> > --
> > Andy Potter
> > blog :http://sqlreportingservices.spaces.live.com
> > info@.(NOSPAM)lakeclaireenterprises.com
> > "Suresh" <Sur...@.discussions.microsoft.com> wrote in message
> >news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> > > Hi Microsoft Sql server reproting services restarts the windows xp
> > > installed
> > > desktops when we try toprintusing theprintoprion in the report.
> > > This is happening for lot of my clients.
> > > How to fix this. This is happening only after the latest update in March.
> > > My company has aroung 40,000 people who will be using the reports
> > > generated
> > > by thereporting servicesmost of them have windows xp with autometic
> > > update
> > > switched on. Hence once the update happnes when they want to take aprint
> > > out
> > > of a report which shown using the MSSRS 2000 in internet explorere and
> > > clicked ontheprinticon in the report windowsystemgets restarted.
> > > Please help
> > > Thanking you
> > > Suresh- Hide quoted text -
> - Show quoted text -|||Hi Shocky,
It is really great. the link you have given actually solved my problem.
Thanks a lot for the help. This was the need of the hour for me.
Once again
Thanking you
Suresh
"Shocky" wrote:
> Suresh,
> We are facing the same problem..
> I was searching around when i got something on this issue in the below
> URL.
> Not sure to what extent it will identify and solve this problem, but
> may be worth a read.
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1480005&SiteID=1
>
> Please let us know if any body gets some solution to this
>
> On Apr 17, 4:08 pm, Suresh <Sur...@.discussions.microsoft.com> wrote:
> > Thanks Andy.
> >
> > But the issue is not with installing the active x.
> >
> > In many systems the active x was installed long before.
> > It was working fine until recently a windws xp update was released.
> > After the update only when clicked on theprinticon in the report displayed
> > in desktops the systems get restarted.
> >
> > So this should be a bug introduced due to the recent update by Microsft
> > update for windows Xp. I am looking for a patch for this.
> >
> > Regards
> > Suresh
> >
> >
> >
> > "Andy Potter" wrote:
> > > Suresh,
> >
> > > The first time you click theprinticon a ActiveX control is installed. You
> > > must have some sort of common desktop configuration that is blowing up when
> > > you try to install this ActiveX.
> >
> > > First thing I would do is look at IE's security settings surrounding the
> > > ActiveX downloading/installing.
> >
> > > --
> > > Andy Potter
> > > blog :http://sqlreportingservices.spaces.live.com
> > > info@.(NOSPAM)lakeclaireenterprises.com
> > > "Suresh" <Sur...@.discussions.microsoft.com> wrote in message
> > >news:099AD7C4-D9BF-420A-A082-C0BB1438A79C@.microsoft.com...
> > > > Hi Microsoft Sql server reproting services restarts the windows xp
> > > > installed
> > > > desktops when we try toprintusing theprintoprion in the report.
> >
> > > > This is happening for lot of my clients.
> > > > How to fix this. This is happening only after the latest update in March.
> >
> > > > My company has aroung 40,000 people who will be using the reports
> > > > generated
> > > > by thereporting servicesmost of them have windows xp with autometic
> > > > update
> > > > switched on. Hence once the update happnes when they want to take aprint
> > > > out
> > > > of a report which shown using the MSSRS 2000 in internet explorere and
> > > > clicked ontheprinticon in the report windowsystemgets restarted.
> >
> > > > Please help
> > > > Thanking you
> > > > Suresh- Hide quoted text -
> >
> > - Show quoted text -
>
>sql

MsSQL Software

is there any free web apps out there that can interface with an SQL Server in real time, like add, edit, delete, update and search the DB?Ummm yeah, any ideas?|||There's always Query Analyzer, the free query tool that ships with MS-SQL Server. Free to use as long as the server you connect to is licensed.

If you're looking for a non-MS tool, just google 'SQL Query tool' and you'll find lots of stuff or check tucows.|||Originally posted by loach
There's always Query Analyzer, the free query tool that ships with MS-SQL Server. Free to use as long as the server you connect to is licensed.

If you're looking for a non-MS tool, just google 'SQL Query tool' and you'll find lots of stuff or check tucows.

Thats not what I am talkin about, I dont want to find an SQL Query tool, I want a full GUI interface to control the DB. All the programs I found in google to view and export data. I dont want a program that just lets you control the DB via SQL statements alone...|||I guess I don't really understand what you're looking for. What is it that you're looking for that Enterprise Manager does not do?|||Originally posted by sabastious
Thats not what I am talkin about, I dont want to find an SQL Query tool, I want a full GUI interface to control the DB. All the programs I found in google to view and export data. I dont want a program that just lets you control the DB via SQL statements alone...

Hello.

See if this help... I have not tried it myself yet.

http://www.msde.biz/msdequery/download.htm|||Originally posted by sabastious
is there any free web apps out there that can interface with an SQL Server in real time, like add, edit, delete, update and search the DB?

myLittleAdmin : http://www.myLittleTools.net/mla_sql

This is a web-based GUI for MS Sql.

best regards|||You can link to your SQL Server database via a Microsoft Access database Access Data Project (.adp file extension) and control many things such as table, view, and procedure creation as well as data manipulation. It acts like a stripped down Enterprise Manager.

But again, why not just use Enterprise Manager?

blindman