Peer-to-peer replication and Oracle real application clusters

Hello,
I have a question I hope can be answered fully.
Some time last year, I attended a Microsoft presentation in Dallas and a sql
server specialist from microsoft (I think his name was srikan) mentioned
during Q&A that SQL Server 2005 has peer-to-peer replication which is a
comparable solution to oracle's real application cluster with some
restriction.
I recently attended another presentation also at Microsoft but this time by
their partner that are suppose to be SQL server experts. This speaker said
that it is not a comparable solution. He gave several reasons and they
seemed to make sense but then again, a microsoft technical specialist said
differently last year.
Did the product change? Who should I listen to? My co-workers say I should
listen to microsoft because they created the product but the other guy seems
to know a lot also and said he used to be an oracle dba. I am confused.
Anybody can help here? I don't want to ask Oracle because they want a lot of
information from me before they will answer and their newsgroup people are
quite unfriendly.
Thank you.
aK.
No, peer-to-peer replication is not a replacement to RAC. Unfortunately,
the TS would be wrong in a literal interpretation. If you look at the basic
data flow, there is some similarity in the solution which disappears when
you start looking a lot deeper.
I don't know a huge amount about RAC, but I understand the basics. With RAC
you are essentially plugging N servers into an Oracle architecture that
access a single database. What you wind up with is theoretically pooling
all of your hardware resources together (memory, processors, network I/O)
which can be basically treated by an application as a single massive server.
They still point to a single database on the backend. You still have to
deal with all of the issues related to changes coming from multiple servers
into a single database which now has to resolve conflicting changes on the
fly and several other implementation related issues.
Peer-to-peer replication is a logical extension to bi-directional
transactional replication. This handles the data layer only. The
replication engine is used to replicate like it says "from everyone - to
everyone". There is ZERO conflict detection or resolution, so your data
changes must be partitioned. If two users were to change the same piece of
data on different servers at the same time, it would create a huge
synchronization issue.
What problem are you trying to solve?
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Angie" <NO_Angie_Kong_SPAM@.hotmail.com> wrote in message
news:ORao5BrMGHA.648@.TK2MSFTNGP14.phx.gbl...
> Hello,
> I have a question I hope can be answered fully.
> Some time last year, I attended a Microsoft presentation in Dallas and a
> sql server specialist from microsoft (I think his name was srikan)
> mentioned during Q&A that SQL Server 2005 has peer-to-peer replication
> which is a comparable solution to oracle's real application cluster with
> some restriction.
> I recently attended another presentation also at Microsoft but this time
> by their partner that are suppose to be SQL server experts. This speaker
> said that it is not a comparable solution. He gave several reasons and
> they seemed to make sense but then again, a microsoft technical specialist
> said differently last year.
> Did the product change? Who should I listen to? My co-workers say I should
> listen to microsoft because they created the product but the other guy
> seems to know a lot also and said he used to be an oracle dba. I am
> confused.
> Anybody can help here? I don't want to ask Oracle because they want a lot
> of information from me before they will answer and their newsgroup people
> are quite unfriendly.
> Thank you.
>
> aK.
>
sql

Peculiar problem with seemingly identical data

Hello,

I have this peculiar problem concerning MS SQL Server.

My company works with an mailing application (ASP) which uses SQL
Server as it's repository. What I want to do is send data directly
from my own application to this SQL Server in order to feed the
mailing application.

To test if this was possible I linked the tables from SQL Server in MS
Access and entered the data. This worked fine and the data was picked
up correctly by the mailing application.

The problem occurs when I send the data from my application (Java
application with JDBC connection). The data is in this case no longer
picked up by the application. The strange thing is that the data which
is entered through Access and the data from the Application look
identical in de database view. The problem also occurs when the data
is send with the tool winSQL and when I view the data in here it still
looks identical.

Even more strange is when I select the record which is not working in
Access and copy it into a new record (only changing the key) it
suddenly works!

Has anyone have an idea how this can be?

Thanks in advance,

Sander Janssen.Sander Janssen (sjanssen@.plex.nl) writes:
> My company works with an mailing application (ASP) which uses SQL
> Server as it's repository. What I want to do is send data directly
> from my own application to this SQL Server in order to feed the
> mailing application.
> To test if this was possible I linked the tables from SQL Server in MS
> Access and entered the data. This worked fine and the data was picked
> up correctly by the mailing application.
> The problem occurs when I send the data from my application (Java
> application with JDBC connection). The data is in this case no longer
> picked up by the application. The strange thing is that the data which
> is entered through Access and the data from the Application look
> identical in de database view. The problem also occurs when the data
> is send with the tool winSQL and when I view the data in here it still
> looks identical.
> Even more strange is when I select the record which is not working in
> Access and copy it into a new record (only changing the key) it
> suddenly works!

I don't have a clue. The thing is, I have no idea by which criterias
your application is picking up data. You need to find this out one
way or another. One way to do this is to use the Profiler to catch
which SQL it is using.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Which JDBC Driver and what version of SQL Server?

"Sander Janssen" <sjanssen@.plex.nl> wrote in message
news:e3b8d8ea.0307040443.5bc4a8d@.posting.google.co m...
> Hello,
> I have this peculiar problem concerning MS SQL Server.
> My company works with an mailing application (ASP) which uses SQL
> Server as it's repository. What I want to do is send data directly
> from my own application to this SQL Server in order to feed the
> mailing application.
> To test if this was possible I linked the tables from SQL Server in MS
> Access and entered the data. This worked fine and the data was picked
> up correctly by the mailing application.
> The problem occurs when I send the data from my application (Java
> application with JDBC connection). The data is in this case no longer
> picked up by the application. The strange thing is that the data which
> is entered through Access and the data from the Application look
> identical in de database view. The problem also occurs when the data
> is send with the tool winSQL and when I view the data in here it still
> looks identical.
> Even more strange is when I select the record which is not working in
> Access and copy it into a new record (only changing the key) it
> suddenly works!
> Has anyone have an idea how this can be?
> Thanks in advance,
> Sander Janssen.|||Hello,

I have found the source of the problem. It isn't as peculiar as I
thought at first though. The problem was that I wrote a date to an
identifier field and the characters ":" were the source of the problem
in the mailing application. When I replaced them with underscores it
all works fine!

Thanks for your help anyway!

Sander Janssen.

PDC - SQLServer Reporting Services Beta Install

I am having difficulty installing the server components of the SQLServer
Reporting Services Beta copy I received at the PDC. My server is the domain
controller for a small home network, and I received the following error:
An error occurred while applying security settings. <machineName>\ASPNET is
not a valid user or group.
This could be a problem with the package, or a problem connecting to a
domain controller on the
network. Check your network connection and click Retry, or Cancel to end
the install.
I have verified that the ASPNET machine account exists - but I suspect a
recent upgrade from .NET framework 1.0 to 1.1 may have influenced this
error. I would like to try changing the account that the Report Server Web
Service runs as, but I don't see an option to accomodate thisoption.
Does anyone have any suggestions?
I have the following installed:
Recently upgraded .NET Framework from 1.0 to 1.1
Windows 2000 Server
SQLServer Standard Edition, SP3a
Thanks in advance,
RobYou might have more luck posting this message on the RS newsgroup.
It's :- microsoft.beta.reporting.services.general
--
HTH
Ryan Waight, MCDBA, MCSE
"Rob Patterson" <rpatterson@.ztr.com> wrote in message
news:uRRZqKGpDHA.384@.tk2msftngp13.phx.gbl...
> I am having difficulty installing the server components of the SQLServer
> Reporting Services Beta copy I received at the PDC. My server is the
domain
> controller for a small home network, and I received the following error:
> An error occurred while applying security settings. <machineName>\ASPNET
is
> not a valid user or group.
> This could be a problem with the package, or a problem connecting to a
> domain controller on the
> network. Check your network connection and click Retry, or Cancel to end
> the install.
> I have verified that the ASPNET machine account exists - but I suspect a
> recent upgrade from .NET framework 1.0 to 1.1 may have influenced this
> error. I would like to try changing the account that the Report Server
Web
> Service runs as, but I don't see an option to accomodate thisoption.
> Does anyone have any suggestions?
> I have the following installed:
> Recently upgraded .NET Framework from 1.0 to 1.1
> Windows 2000 Server
> SQLServer Standard Edition, SP3a
> Thanks in advance,
> Rob
>|||How do I subscribe to microsoft.beta.reporting.services.general
I have a similar problem, but I am unable to subscribe.
Thanks,
Hanna

pbm while connecting to a remote server

Hi,
I have a pbm while connecting to the remote SQL server.
Recently we hired one win2003 based Dedicated server and installed SQl
server 2000. I have the sa password and the ip of the server, and when i
connect to this server from my local machine by configuring client n/w
utility, its giving me the error. like SQL server Does not exists ?
What shall i do ? i've disabled the firewall also, but not successful yet.
Also one more problem. The version i've installed is Enterprise Edition, and
will there be any problem if i uninstall it and reinstall the Standard
edition?
Thanking u in advance LaraHi
You should have no problems with un-installing Enterprise Edition and
re-installing Standard if you are not using any of the additional features
that it has. You may want to look at
http://support.microsoft.com/defaul...b;en-us;Q314546 for
transferring logins and dealing with Orphaned users if you have them. Make
sure that the new version is service packed and patched to the same level.
Backing up your database before un-installation will make sure that you have
a safe copy.
When you install the new system make sure that the correct protocols are
listed on the server's server network utilities. Check that you can ping the
server from your client and that the client also has the correct network
protocols. You may want to try SQLPing or SQLRecon to see if the server is
contactable.
John
"lara" <lara@.l.com> wrote in message
news:eOx2EApZFHA.1088@.TK2MSFTNGP14.phx.gbl...
> Hi,
> I have a pbm while connecting to the remote SQL server.
> Recently we hired one win2003 based Dedicated server and installed SQl
> server 2000. I have the sa password and the ip of the server, and when i
> connect to this server from my local machine by configuring client n/w
> utility, its giving me the error. like SQL server Does not exists ?
> What shall i do ? i've disabled the firewall also, but not successful yet.
> Also one more problem. The version i've installed is Enterprise Edition,
> and
> will there be any problem if i uninstall it and reinstall the Standard
> edition?
>
> Thanking u in advance Lara
>|||I missed out the link for SQLPing and SQLRecon!
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:%23nvI0tqZFHA.1404@.TK2MSFTNGP09.phx.gbl...
> Hi
> You should have no problems with un-installing Enterprise Edition and
> re-installing Standard if you are not using any of the additional features
> that it has. You may want to look at
> http://support.microsoft.com/defaul...b;en-us;Q314546 for
> transferring logins and dealing with Orphaned users if you have them. Make
> sure that the new version is service packed and patched to the same level.
> Backing up your database before un-installation will make sure that you
> have a safe copy.
> When you install the new system make sure that the correct protocols are
> listed on the server's server network utilities. Check that you can ping
> the server from your client and that the client also has the correct
> network protocols. You may want to try SQLPing or SQLRecon to see if the
> server is contactable.
> John
>
> "lara" <lara@.l.com> wrote in message
> news:eOx2EApZFHA.1088@.TK2MSFTNGP14.phx.gbl...
>|||Thanks John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:eNJEsvqZFHA.3572@.TK2MSFTNGP12.phx.gbl...
> I missed out the link for SQLPing and SQLRecon!
> http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=26
> John
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:%23nvI0tqZFHA.1404@.TK2MSFTNGP09.phx.gbl...
features
Make
level.
i
Edition,
>

PB to connect a remote.

hi,

last week I posted a thread to explain that I was unable tu access a remote sqlserver from my personnal computer running wsindows XP.
I had a problem with my motherboard which obliged me to change it. I did, and decided to format my hard drive and reinstal only the programs needed, once upon SQL server could connect to my DB. I first instal XP, then the SP1 and after sql server. Then i configured the client network utility using an alias and giving the IP. It functionned well. Then I instal the soft I need (Sharp developp, webmatrix, flash XP (ftp), Together and office XP) but I was configuring Outlook when I got and CPU FAN warning. 256 mega de ram later, I was sure it will run like it did saturday but it was'nt. It make the same error as before the motherboard changing. So I reformat my hard drive and I don't understand what could it make weel run on satruday and the shunt down on monday.

so If you have an Idea of what to do, please help me,

wozoiI reinstall XP but not the SP1 and just SQL server it make the same eternal error connection open conect()).

somebody get an idea.

wozoi|||Please post the exact error and also any entries in the event log and your sql server log.|||hi and thanks,

On the remote server ther is no trace of a connection trying,
and i don't find on my computer the event log you asks.

In the Attachement you will find the screen shot and the translation (because I'm french) of the error.

Could you reply me where can i find the event log to send it to you.

thanks for your help.

pierre jean

Patching SQLServer/MSDE

Patching SQLServer/MSDE
We are developing a desktop application that will use an MSDE database. The
data in the DB we deploy cannot be read by users, or administrators of the b
ox or other SQL Server admins. To accomplish this, we have learned we would
have to install a separate
instance of SQLServer/MSDE on the user's PC (or, alternately, encrypt the da
tabase).
The downside to a separate instance is we would be responsible to apply any
SQL Server patches to our instance. Our software is given to our customers,
and we have no control over their machines, so we will have to issue servic
e patches for our software
that contain the SQL Server patches as they come out.
My question is this: Obviously, it will be difficult for us to get patches o
f our software out there immediately after each SQL Server patch is released
my Microsoft. Are there threats that SQL Server remedy that can possibly ha
ve an adverse effect on sof
tware/hardware outside of the our database that is using the SQL Server inst
ance? I'm wondering about our liability if say, we release our version of a
patch 1-2 months after Microsoft releases their patch. I know our database
may be threatened, but is
there the possibility the user's machines/network would also be threatened i
f certain patches are not installed in a timely matter? I understand how th
is would be a major issue if we were talking about patches to IIS, but not
so sure about SQL Server.
Any thoughts on this are greatly appreciated.
Thanks!MSDE can be configured to listen only on Shared Memory. This will limit
your exposure from
external machines. So, other machines won't be able to connect to your
instance of MSDE, since
it's not listening on TCP or Named Pipes. Only local connections would
succeed.
MBSA 1.2 can be used to scan the local machine to see if it needs any SQL
related security fixes.
This could be documented in your application notes.
http://www.microsoft.com/technet/se...s/mbsahome.mspx
You can also find out Best Practices on the web ;
http://www.microsoft.com/technet/pr...n/sp3sec00.mspx
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Password's case sensitivity

Hi,
somehow my Sql Server's passwors are not case sensitive. I thought sql
server's login passwords are case sensitive.
Am I worng?
How do I change my SQL Server back to the case sensitive passwords?
Please help..
Thank you
SamHi
Passwords case sensitivity is based on the collation of the installation. If
you install with a non-case sensitive collation, the password will not be
cases sensitive.
Regards
Mike
"sam" wrote:

> Hi,
> somehow my Sql Server's passwors are not case sensitive. I thought sql
> server's login passwords are case sensitive.
> Am I worng?
> How do I change my SQL Server back to the case sensitive passwords?
> Please help..
> Thank you
> Sam|||Password case-sensitivity is determined by the default collation for the SQL
Server instance. It appears you have a case-insensitive collation.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:BDB6FA4B-D047-438F-A850-0E3FD0A8F49B@.microsoft.com...
> Hi,
> somehow my Sql Server's passwors are not case sensitive. I thought sql
> server's login passwords are case sensitive.
> Am I worng?
> How do I change my SQL Server back to the case sensitive passwords?
> Please help..
> Thank you
> Sam|||Thank you for your response. I think the Earlier I used all the SQL servers
which are upgraded from 7.0 to 2K and so the defautl collation of 7.0 was a
case sensitive. (Not usre right now).
But if I want to keep all my client data and other code to be case
-insensitive but all my login passwords to be case sensitive , can I do that
?
How can I do that?
Please let me know..
Thank you again..
Sam
"Dan Guzman" wrote:

> Password case-sensitivity is determined by the default collation for the S
QL
> Server instance. It appears you have a case-insensitive collation.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:BDB6FA4B-D047-438F-A850-0E3FD0A8F49B@.microsoft.com...
>
>|||To change the instance default collation after installation, you'll need to
either reinstall or rebuild the master database. This will create new
master, msdb and model databases.
Although you can run with mixed collations, this can lead to problems. The
tempdb collation will be the instance default so you might get errors due to
collation conflicts when using temp tables.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:96622B87-A747-4E23-8593-27221C2C10BD@.microsoft.com...[vbcol=seagreen]
> Thank you for your response. I think the Earlier I used all the SQL
> servers
> which are upgraded from 7.0 to 2K and so the defautl collation of 7.0 was
> a
> case sensitive. (Not usre right now).
> But if I want to keep all my client data and other code to be case
> -insensitive but all my login passwords to be case sensitive , can I do
> that?
> How can I do that?
> Please let me know..
> Thank you again..
> Sam
> "Dan Guzman" wrote:
>|||Thanks Dan,
But I think I did not put my question clearly. My Apologies.
I want to keep the collation of all the DBs on the server same as what I
have at present (case in-sensitive) but only all my login passwords should b
e
case sensitive.
Can I do that?
How?
Thank you
Sam
"Dan Guzman" wrote:

> To change the instance default collation after installation, you'll need t
o
> either reinstall or rebuild the master database. This will create new
> master, msdb and model databases.
> Although you can run with mixed collations, this can lead to problems. Th
e
> tempdb collation will be the instance default so you might get errors due
to
> collation conflicts when using temp tables.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:96622B87-A747-4E23-8593-27221C2C10BD@.microsoft.com...
>
>|||Running mixed collations is the only way to have case-sensitive passwords
and case-insensitive user database collations. The default collation of
your existing databases will not be changed after you reattach following a
master database rebuild or SQL Server reinstall.
However, as I mentioned in my previous response, mixed collations will have
other consequences. If you feel compelled to try this, be sure to
thoroughly test your applications before implementing this in production.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:B4EB814F-DCAD-4AF1-AB66-11C821BFD09D@.microsoft.com...[vbcol=seagreen]
> Thanks Dan,
> But I think I did not put my question clearly. My Apologies.
> I want to keep the collation of all the DBs on the server same as what I
> have at present (case in-sensitive) but only all my login passwords should
> be
> case sensitive.
> Can I do that?
> How?
> Thank you
> Sam
> "Dan Guzman" wrote:
>|||I understand your concern and thank you for your response.
Bu insterad of rebuilding my master database, Can I change the collation of
the password column of the sysxlogin table?
This is just a guess. I think you must have thought of this but I still want
to ask you this question.
"Dan Guzman" wrote:

> Running mixed collations is the only way to have case-sensitive passwords
> and case-insensitive user database collations. The default collation of
> your existing databases will not be changed after you reattach following a
> master database rebuild or SQL Server reinstall.
> However, as I mentioned in my previous response, mixed collations will hav
e
> other consequences. If you feel compelled to try this, be sure to
> thoroughly test your applications before implementing this in production.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:B4EB814F-DCAD-4AF1-AB66-11C821BFD09D@.microsoft.com...
>
>|||> Bu insterad of rebuilding my master database, Can I change the collation
> of
> the password column of the sysxlogin table?
Changing system table schema is not supported so you would this is at your
own risk. The supported method is a mixed collation environment with a
case-sensitive instance default collation and case-insensitive collation for
user databases. Of course, mixed collation caveats apply.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:D516F2B3-79BF-414E-B005-88AB683F5DD5@.microsoft.com...[vbcol=seagreen]
>I understand your concern and thank you for your response.
> Bu insterad of rebuilding my master database, Can I change the collation
> of
> the password column of the sysxlogin table?
> This is just a guess. I think you must have thought of this but I still
> want
> to ask you this question.
> "Dan Guzman" wrote:
>|||Thank you Dan,
I will try this in the development environment and then see how it works
before changing the collation for any thing else.
Thank you once again for your time and response.
Sam
"Dan Guzman" wrote:

> Changing system table schema is not supported so you would this is at your
> own risk. The supported method is a mixed collation environment with a
> case-sensitive instance default collation and case-insensitive collation f
or
> user databases. Of course, mixed collation caveats apply.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:D516F2B3-79BF-414E-B005-88AB683F5DD5@.microsoft.com...
>
>

password for sa was changed spontaneously

Hello!

We are running MS SQLServer 7.0 with ASP on Win 2k Server.
Today suddenly the Web server couldn't connect to the DB Server
because the password for sa was wrong.
We found out that the password was changed.

Is it some kind of hacking thing or just normal password expiration?
The same thing happended several month ago.

Thanks.

SamSam Kong (ssk@.chol.net) writes:
> We are running MS SQLServer 7.0 with ASP on Win 2k Server.
> Today suddenly the Web server couldn't connect to the DB Server
> because the password for sa was wrong.
> We found out that the password was changed.
> Is it some kind of hacking thing or just normal password expiration?
> The same thing happended several month ago.

There is no password expiration in SQL7. So that means that somebody
changed the password for you.

I would recommend that you change to Windows Authentication and turn
off SQL Authentication. I would also recommand that the web server
does not log with an account that has sysadm privileges. Preferrably
it should no special rights, but access to the SQL objects it needs
to access. (And that should ideally only be stored procedures!).

Finally, if the SQL Server is exposed on the Internet, you should
stick it behind a firewall.

All these precautions increase your security and decreases the risk
for malign attacks.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Password Encryption in XML File

I am unable to encrypt password of sqlserver database in XML file by Package Configuration in SSIS.

I think that is not possible (though it might be possible if you develop something). According to the SSIS help you can either save the config file in SQL Server or use Windows access control lists to protect access to your config file. See ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.SQLSVR.v9.de/extran9/html/2e3ddea9-5289-4289-a70e-11c018f34977.htm|||Yes in config file i have to put the password manually in config file.If i choose only connection string property in configuration wizard then it is working fine.But When i reset the server password then it fails.So i have to give the password.But unable to encrypt it for security reasons.

Password Changes in SQLServer

Is there a way to find out if a user has not changed his/her passord in more than 90 days. I need to find the date of last password change and days since last password changes.
Thanks in Advance.The only way that I know to do this is to create a table with three columns, one for the login name, one for the current (hashed) password, and one for the date the last change was detected. Periodically (probably daily) check to see if there are either new logins or new password values.

-PatP|||Well, I wouldn't say that that's the only way. In fact, all you need is 2 columns, login and lastchanged. I've gone a little further and modified 3 system procedures, - sp_password, sp_addlogin, and sp_droplogin by implementing password aging and compexity. By having the table above you can incorporate UPDATE, INSERT, and DELETE into/from it respectively.|||You've got a point, but modifying system supplied stored procedures or triggers will get you a reserved seat in the "naughty" section in my opinion. I wouldn't consider recommending that, and probably wouldn't permit it in any environment that I can control.

-PatP|||Just use trusted connections|||You've got a point, but modifying system supplied stored procedures or triggers will get you a reserved seat in the "naughty" section in my opinion. I wouldn't consider recommending that, and probably wouldn't permit it in any environment that I can control.

-PatPThere are no system triggers. Modifying system stored procedures? If you know what you're doing, and if your Change Management process is in place, - I see no problem with that. After all, it's those modifications that prompted Yukon development team to implement...well, you'll see it in the next CTP.|||Come on...you can say it....

Better yet, if you're interested download 2005 BOL|||Too much inaccurate info there. It hasn't matched a single Beta-2 built yet ;)