显示标签为“windows”的博文。显示所有博文
显示标签为“windows”的博文。显示所有博文

2012年3月27日星期二

ANYONE PLEASE - Local Synchronization Between SQL Mobile and Local SQL Database

Hi Everyone

I am at the stage of architecting my solution

My goal is to develop the system on a windows application and pda

There is a central server which will create a publication called inventory

The laptops which host the windows application will be subscribers to the central server using merge replication

The client now wants the PDA using SQL Mobile to synchronize with the local subscirber database on the laptop using active sync. They dont want to do it via WIFI to the IIS Server at the central server

I have been reading for days and I am still unsure whether this is possible to do.

I know Appforge provide a conduit for palm to access synchronization but not local sql databases

I would appreciate your help immensley

Can anyone please help me

|||

If you build your mobile application using VS2005 and SQL Mobile, you can use merge replication between your server-side publication and SQL Mobile. The SQL Mobile Books OnLine are the first place to start - read the section on merge replication.

-Darren Shaffer

|||

Hi Darren

Yes I got my sql mobile to synchronize successfully with the local desktop sql database called "Inventory"

However I have a new problem

I would like to have the desktop replicating with the server for database "Inventory"

I also got this to work seperately

I would now want the SQL mobile database to replicate with the local desktop database "Inventory" which inturn will replicate with the server copy called "Inventory"

I would like to have both replication scenarios joined together. I know that most people will say get the SQL mobile to talk directly to the server but this is the most expensive scenario I believe

Is this possible?

Thankyou for your earlier post

Touraj

|||

Touraj,

Sorry for not reading your post more closely - I see what you are trying to do now. You want to have a 3 tier merge replication going on. Yes, this is possible, but the database on the laptop is going to have to be SQL Server 2005, not SQL Express. The way it would have to work is this:

The laptop would have to have IIS installed and the SQL Mobile server tools. As far as the mobile app is concerned, the laptop is the publisher. On the laptop, you have a subscription to the central server in a replication relationship. You would turn around and create a publication on the laptop with the same articles that are in the subscription to the central server. You would need to be extremely careful with uniqueness in this situation - I would avoid identity columns and use GUIDs for everything in this app domain.

Is there any chance that both the laptops and the PDAs can be subscribers to the central server? That would be a much easier implementation, but it is possible to do what you suggested with the extra tier.

-Darren

|||

Hi Darren

Thankyou again for your kind assistance

Yes you are right. It would be easier and 'cheaper' to get the PDA to synch with the central server via the servers IIS process

I am tossing up between a i-Mate and iPaq 4700. I would be interested to know if you have a preference over the two

Thanks from sunny Australia.

Touraj

|||

I think both i-Mate and HP make great devices - I have not had any trouble with SQL Mobile on my JasJar or on a variety of iPaqs. My WM5 JasJar seems a little sluggish overall compared to a Dell Axim X50v (WM5), which others have noted as well. Not slow, just not instant to respond to input. I have not had specific experience with the 4700. There are some public newsgroups (microsoft.public.pocketpc.developer) where people tend to talk more about specific devices and you could use Google Advanced Groups search to get previous opinions on the 4700.

-Darren

2012年3月22日星期四

Any way to track who/when data was deleted ?

Hello,
I'm using merge replication with SQL Server 2000 on Windows 2003 server,
with MSDE2000A clients with anon pull subscriptions.
Some data has been (mysteriously) deleted and I would like to find out more
about who/when it was deleted.
Is there any way (system tables, transaction log ?) of determining who/when
certain records were deleted ?
I noticed that in my publication DB the MSmerge_tombstone table has a field
that shows either "user delete" or "system delete" - what is a System
Delete?
Thanks for your help.
Darren
No, you have to write custom triggers to track this information.
What you will get is the user that makes this change on the local server,
and then the account your merge agent runs under. So if you make a change on
your publisher, there is no way to have this user name transferred to the
subcriber, unless you also replicated an audit table.
User delete is when a user deletes a record, system delete is when a system
process (normally in response to a conflict) deletes the record.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Darren Wallace" <darren@.pcresources.com.au> wrote in message
news:eQdrh$FmEHA.3524@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I'm using merge replication with SQL Server 2000 on Windows 2003 server,
> with MSDE2000A clients with anon pull subscriptions.
> Some data has been (mysteriously) deleted and I would like to find out
more
> about who/when it was deleted.
> Is there any way (system tables, transaction log ?) of determining
who/when
> certain records were deleted ?
> I noticed that in my publication DB the MSmerge_tombstone table has a
field
> that shows either "user delete" or "system delete" - what is a System
> Delete?
> Thanks for your help.
> Darren
>
|||www.lumigent.com
"Darren Wallace" <darren@.pcresources.com.au> wrote in message
news:eQdrh$FmEHA.3524@.TK2MSFTNGP12.phx.gbl...
> Hello,
> I'm using merge replication with SQL Server 2000 on Windows 2003 server,
> with MSDE2000A clients with anon pull subscriptions.
> Some data has been (mysteriously) deleted and I would like to find out
more
> about who/when it was deleted.
> Is there any way (system tables, transaction log ?) of determining
who/when
> certain records were deleted ?
> I noticed that in my publication DB the MSmerge_tombstone table has a
field
> that shows either "user delete" or "system delete" - what is a System
> Delete?
> Thanks for your help.
> Darren
>

2012年3月19日星期一

Any way to disable SQL logins after failed tries?

We're using a canned app that only uses SQL Server logins (it will NOT use Windows logins to access SQL Server)

SQL Server logins seem to lack even the most rudimentary security features such as expiring passwords and automatic disabling after a set number of failed logins. Bad. Bad Microsoft.

Has anyone figured out a way to graft this on after-the-fact?

I can do it in an awkward fashion by auditing failed logins and going back to read the error log, but this isn't real time by any stretch.To the best of my knowledge, there is no innate feature in MS SQL that will allow you manage SQL Server logins as you wish. This lack has been noted before (cross your fingers, MS will deal with this in Yukon).

We wrote a custom app and created this kind of failed-login checking, but that does not sound like an option for you.

Can you do something with a scheduled job at the SQL error log (you'd have to enable logging of failed login attempts)?

I think there is a way to load the error log as a table. Then you could search for failed logins and (if the number exceeded your threshold) disable it.

I think it's doable, but I have not had the need to accomplish this particular task.

Regards,

hmscott|||Originally posted by hmscott
To the best of my knowledge, there is no innate feature in MS SQL that will allow you manage SQL Server logins as you wish. This lack has been noted before (cross your fingers, MS will deal with this in Yukon).

We wrote a custom app and created this kind of failed-login checking, but that does not sound like an option for you.

Can you do something with a scheduled job at the SQL error log (you'd have to enable logging of failed login attempts)?

I think there is a way to load the error log as a table. Then you could search for failed logins and (if the number exceeded your threshold) disable it.

I think it's doable, but I have not had the need to accomplish this particular task.

Regards,

hmscott

I doubt it...since SQL Server "security" is not the way to go...you can "See" passwords as plain as day...oh, I forgot...M$ describes this as a feature....

Any video/other tutorials for ASP.Net and ReportViewer control?

I have figured out how to build a report for reportserver - I even have a
video that tells me how to use the reportviewer in a Windows app, but I need
to learn how to do the basics in an ASP.Net page, with the ReportViewer
control.
Are there any basic, step by step web pages that show this, or even better -
any videos to checkout on the web?On Jan 18, 1:02 pm, "Elmo Watson" <s...@.here.com> wrote:
> I have figured out how to build a report for reportserver - I even have a
> video that tells me how to use the reportviewer in a Windows app, but I need
> to learn how to do the basics in an ASP.Net page, with the ReportViewer
> control.
> Are there any basic, step by step web pages that show this, or even better -
> any videos to checkout on the web?
These articles might be helpful.
http://www.aspfree.com/c/a/ASP.NET/Binding-Data-to-the-ReportViewer-Control-Dynamically-in-ASPNET-20/
http://msdn2.microsoft.com/en-us/library/ms252104(VS.80).aspx
Regards,
Enrique Martinez
Sr. Software Consultant

2012年3月6日星期二

Any performance benefits using Windows 2003 ?

Currently using Windows 2000 AS and SQL 2000 EE. Would we get any
performance benefits if we upgrade the OS to Windows 2003 ? If so , what are
the benefits if any with regards to SQL ServerTry this URL
http://www.microsoft.com/sql/techinfo/planning/winsvr2003benefits.asp
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23PaMDpMlDHA.684@.TK2MSFTNGP09.phx.gbl...
> Currently using Windows 2000 AS and SQL 2000 EE. Would we get any
> performance benefits if we upgrade the OS to Windows 2003 ? If so , what
are
> the benefits if any with regards to SQL Server
>|||In article <#PaMDpMlDHA.684@.TK2MSFTNGP09.phx.gbl>, "Hassan" <fatima_ja@.hotmail.com> wrote:
>Currently using Windows 2000 AS and SQL 2000 EE. Would we get any
>performance benefits if we upgrade the OS to Windows 2003 ? If so , what are
>the benefits if any with regards to SQL Server
>
I don't recall exactly where, but there was a review written recently that
indicated an average 20% performance increase just from upgrading an existing
Win2k SQL 2k box to Win2003.
Apparantly, this had to do with VASTLY improved file i/o and network interface
implementation.
Anyone here rmember this review and/or have the link to it?|||Hi,
Here's a list of what is changed:
http://www.sql-server-performance.com/operating_system_tuning_w2003.asp
--
Regards,
Kristofer Gafvert - IIS MVP
http://www.ilopia.com - FAQ & Tutorials for Windows Server 2003, and SQL
Server 2000
Reply to newsgroup only. Remove NEWS if you must reply by email, but please
do not.
Problems with spam and viruses? See
http://www.ilopia.com/security/newsposting.aspx
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23PaMDpMlDHA.684@.TK2MSFTNGP09.phx.gbl...
> Currently using Windows 2000 AS and SQL 2000 EE. Would we get any
> performance benefits if we upgrade the OS to Windows 2003 ? If so , what
are
> the benefits if any with regards to SQL Server
>

Any other patch need to installed besides SP3a?

Hi,
I installed SP3a for MS SQL 2000. Do I need to install any other tools to prevent from hacking?
e.g. IIS Lockdown Tool for windows 2000 server IIS 5
Thanks for advice
You should check all your servers with these security tools.
http://www.microsoft.com/downloads/d...displaylang=en
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Tom" <kerocow@.yahoo.com> wrote in message
news:EEC32889-130C-4327-8AA2-A1F41BFD1430@.microsoft.com...
> Hi,
> I installed SP3a for MS SQL 2000. Do I need to install any other tools to
prevent from hacking?
> e.g. IIS Lockdown Tool for windows 2000 server IIS 5
> Thanks for advice
|||Tom,
You might want to install the MS03-031 security update.
http://www.microsoft.com/technet/sec.../MS03-031.mspx
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Tom wrote:
> Hi,
> I installed SP3a for MS SQL 2000. Do I need to install any other tools to prevent from hacking?
> e.g. IIS Lockdown Tool for windows 2000 server IIS 5
> Thanks for advice
|||Thanks for help

Any other patch need to installed besides SP3a?

Hi,
I installed SP3a for MS SQL 2000. Do I need to install any other tools to pr
event from hacking?
e.g. IIS Lockdown Tool for Windows 2000 server IIS 5
Thanks for adviceYou should check all your servers with these security tools.
CDE4D933600&displaylang=en" target="_blank">http://www.microsoft.com/downloads/...&displaylang=en
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Tom" <kerocow@.yahoo.com> wrote in message
news:EEC32889-130C-4327-8AA2-A1F41BFD1430@.microsoft.com...
> Hi,
> I installed SP3a for MS SQL 2000. Do I need to install any other tools to
prevent from hacking?
> e.g. IIS Lockdown Tool for Windows 2000 server IIS 5
> Thanks for advice|||Tom,
You might want to install the MS03-031 security update.
http://www.microsoft.com/technet/se...n/MS03-031.mspx
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Tom wrote:
> Hi,
> I installed SP3a for MS SQL 2000. Do I need to install any other tools to
prevent from hacking?
> e.g. IIS Lockdown Tool for Windows 2000 server IIS 5
> Thanks for advice|||Thanks for help

2012年2月25日星期六

Any known issues with AWE and Windows 2003

Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
it. Does anyone know more or a KB article ?I am not sure, but we are currently experinceing performance issues
since going to SP1. See my post in this group, Too Much RAM SQL Server
2000?|||Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one just
hit us pretty good:
http://support.microsoft.com/defaul...kb;en-us;899599
Darian Miller
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>|||Hi
Darian, how busy was your SQL Server to have this problem?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> just
> hit us pretty good:
> http://support.microsoft.com/defaul...kb;en-us;899599
> Darian Miller
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>|||Here are a few:
http://support.microsoft.com/defaul...kb;en-us;895575
http://support.microsoft.com/defaul...kb;en-us;838765
Adrian
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>|||So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> Here are a few:
> http://support.microsoft.com/defaul...kb;en-us;895575
> http://support.microsoft.com/defaul...kb;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
fixes[vbcol=seagreen]
>|||Actually, a PAE fix for Win2K3 has also been released as part of a Security
Hotfix Critical Update:
Microsoft Security Bulletin MS04-032
Security Update for Microsoft Windows (840987)
http://www.microsoft.com/technet/se...n/ms04-032.mspx
Sincerely,
Anthony Thomas
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> Here are a few:
> http://support.microsoft.com/defaul...kb;en-us;895575
> http://support.microsoft.com/defaul...kb;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
fixes[vbcol=seagreen]
>|||The issues with w2k3 at very small compared to NT 4.0 and w2k.
We found that most of the 'issues' with w2k3 are NT 4.0 MCSE's not
understanding security.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
> So with all these issues with Win2K3, what does MS have to say ? Do
> companies move forward on Win2K3 ?
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> fixes
>

Any known issues with AWE and Windows 2003

Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
it. Does anyone know more or a KB article ?I am not sure, but we are currently experinceing performance issues
since going to SP1. See my post in this group, Too Much RAM SQL Server
2000?|||Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one just
hit us pretty good:
http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
Darian Miller
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>|||Hi
Darian, how busy was your SQL Server to have this problem?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> just
> hit us pretty good:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
> Darian Miller
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>> Heard there are issues with AWE and Windows 2003 and SP1 for Windows
>> fixes
>> it. Does anyone know more or a KB article ?
>>
>|||We're still documenting the deal, but the 'security feature' actually seems
to cause a lot of increased traffic due to the many retry attempts. (We're
in the 3-500 batch requests/second range normally.)
Basically it appears that the client makes a successful connection to the
server and the connection is immediately forcibly dropped by the server
causing "General Network Error" on DBNETLIB ConnectionWrite (send())
The errors were coming in what we thought was fairly randomly but apparently
was based on peak levels set by this security feature. If the server thinks
the source is attempting a denial of service attack then it decides to drop
the network traffic, without notice of any kind (no event logging.) What I
would think it should do is if it thinks a source is attempting a denial of
service, then it should block all packets from the source, not just a few of
the peak ones, and it should document that it has automatically stepped in
to "save the day"... Much more difficult to track down they way it is
currently implemented. We were on the phone with Microsoft for over 8 hours
over the past two days on this particular problem and they didn't come
across the solution - we had to find it and tell them about it.
If you have SQL Server on a Windows 2003 Server with SP1, then I'd suggest
setting the registry setting referenced in the knowledge based article,
especially since it's highly likely that your SQL Server is protected from
outside connections to begin with.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Add DWORD: SynAttackProtect, value 0
I'm mainly just venting...but it's ludicrous to have this sort of 'feature'
implemented the way it is. Security needs to be a focus, but goodness sakes
you need to have some common sense about it. What's the point of dropping
'some' packets if it's a suspected DOS attack? They might have their
reasons, but there is no reason to not have a log entry stating that they
intentionally dropped network traffic. A simple "Suspected
denial-of-service attack detected, taking corrective action" would have
saved many hours of work.
Time for a drink! :)
Darian Miller
darian
@.
darianmiller
.com
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23EMfUSHbFHA.720@.TK2MSFTNGP15.phx.gbl...
> Hi
> Darian, how busy was your SQL Server to have this problem?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Darian Miller" <darianmiller@.online.nospam> wrote in message
> news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> > Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> > just
> > hit us pretty good:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
> >
> > Darian Miller
> >
> >
> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> > news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> >> Heard there are issues with AWE and Windows 2003 and SP1 for Windows
> >> fixes
> >> it. Does anyone know more or a KB article ?
> >>
> >>
> >
> >
>|||Here are a few:
http://support.microsoft.com/default.aspx?scid=kb;en-us;895575
http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
Adrian
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>|||Hi
Very interesting. Thanks for sharing this, I think you have saved many
people a lot of time.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:%23A65roHbFHA.3040@.TK2MSFTNGP14.phx.gbl...
> We're still documenting the deal, but the 'security feature' actually
> seems
> to cause a lot of increased traffic due to the many retry attempts.
> (We're
> in the 3-500 batch requests/second range normally.)
> Basically it appears that the client makes a successful connection to the
> server and the connection is immediately forcibly dropped by the server
> causing "General Network Error" on DBNETLIB ConnectionWrite (send())
> The errors were coming in what we thought was fairly randomly but
> apparently
> was based on peak levels set by this security feature. If the server
> thinks
> the source is attempting a denial of service attack then it decides to
> drop
> the network traffic, without notice of any kind (no event logging.) What
> I
> would think it should do is if it thinks a source is attempting a denial
> of
> service, then it should block all packets from the source, not just a few
> of
> the peak ones, and it should document that it has automatically stepped in
> to "save the day"... Much more difficult to track down they way it is
> currently implemented. We were on the phone with Microsoft for over 8
> hours
> over the past two days on this particular problem and they didn't come
> across the solution - we had to find it and tell them about it.
> If you have SQL Server on a Windows 2003 Server with SP1, then I'd suggest
> setting the registry setting referenced in the knowledge based article,
> especially since it's highly likely that your SQL Server is protected from
> outside connections to begin with.
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> Add DWORD: SynAttackProtect, value 0
> I'm mainly just venting...but it's ludicrous to have this sort of
> 'feature'
> implemented the way it is. Security needs to be a focus, but goodness
> sakes
> you need to have some common sense about it. What's the point of dropping
> 'some' packets if it's a suspected DOS attack? They might have their
> reasons, but there is no reason to not have a log entry stating that they
> intentionally dropped network traffic. A simple "Suspected
> denial-of-service attack detected, taking corrective action" would have
> saved many hours of work.
> Time for a drink! :)
> Darian Miller
>
> darian
> @.
> darianmiller
> .com
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23EMfUSHbFHA.720@.TK2MSFTNGP15.phx.gbl...
>> Hi
>> Darian, how busy was your SQL Server to have this problem?
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "Darian Miller" <darianmiller@.online.nospam> wrote in message
>> news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
>> > Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
>> > just
>> > hit us pretty good:
>> > http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
>> >
>> > Darian Miller
>> >
>> >
>> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
>> > news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>> >> Heard there are issues with AWE and Windows 2003 and SP1 for Windows
>> >> fixes
>> >> it. Does anyone know more or a KB article ?
>> >>
>> >>
>> >
>> >
>>
>|||"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
just
> hit us pretty good:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
Thanks for that tip. We have a high-volume SQL instance where we're seeing
behavior similar to what the KB article describes. We're not running with
any OS service pack, but we do apply the monthly patches. I wonder if the
DOS-preventing "security feature" has been included in any of those.|||Yes, I believe it has been included in a security fix. If you've seen these
messages, apply the registry setting and they go away immediately after a
restart.
"Karen Collins" <kcollins5@.tampabay.rr.com> wrote in message
news:eL3p4TNbFHA.3040@.TK2MSFTNGP14.phx.gbl...
> "Darian Miller" <darianmiller@.online.nospam> wrote in message
> news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> > Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> just
> > hit us pretty good:
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
>
> Thanks for that tip. We have a high-volume SQL instance where we're
seeing
> behavior similar to what the KB article describes. We're not running with
> any OS service pack, but we do apply the monthly patches. I wonder if the
> DOS-preventing "security feature" has been included in any of those.
>|||I hope so!
Darian
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:ehVr8SLbFHA.2124@.TK2MSFTNGP14.phx.gbl...
> Hi
> Very interesting. Thanks for sharing this, I think you have saved many
> people a lot of time.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Darian Miller" <darianmiller@.online.nospam> wrote in message
> news:%23A65roHbFHA.3040@.TK2MSFTNGP14.phx.gbl...
> > We're still documenting the deal, but the 'security feature' actually
> > seems
> > to cause a lot of increased traffic due to the many retry attempts.
> > (We're
> > in the 3-500 batch requests/second range normally.)
> >
> > Basically it appears that the client makes a successful connection to
the
> > server and the connection is immediately forcibly dropped by the server
> > causing "General Network Error" on DBNETLIB ConnectionWrite (send())
> >
> > The errors were coming in what we thought was fairly randomly but
> > apparently
> > was based on peak levels set by this security feature. If the server
> > thinks
> > the source is attempting a denial of service attack then it decides to
> > drop
> > the network traffic, without notice of any kind (no event logging.)
What
> > I
> > would think it should do is if it thinks a source is attempting a denial
> > of
> > service, then it should block all packets from the source, not just a
few
> > of
> > the peak ones, and it should document that it has automatically stepped
in
> > to "save the day"... Much more difficult to track down they way it is
> > currently implemented. We were on the phone with Microsoft for over 8
> > hours
> > over the past two days on this particular problem and they didn't come
> > across the solution - we had to find it and tell them about it.
> >
> > If you have SQL Server on a Windows 2003 Server with SP1, then I'd
suggest
> > setting the registry setting referenced in the knowledge based article,
> > especially since it's highly likely that your SQL Server is protected
from
> > outside connections to begin with.
> >
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> > Add DWORD: SynAttackProtect, value 0
> >
> > I'm mainly just venting...but it's ludicrous to have this sort of
> > 'feature'
> > implemented the way it is. Security needs to be a focus, but goodness
> > sakes
> > you need to have some common sense about it. What's the point of
dropping
> > 'some' packets if it's a suspected DOS attack? They might have their
> > reasons, but there is no reason to not have a log entry stating that
they
> > intentionally dropped network traffic. A simple "Suspected
> > denial-of-service attack detected, taking corrective action" would have
> > saved many hours of work.
> >
> > Time for a drink! :)
> >
> > Darian Miller
> >
> >
> >
> > darian
> > @.
> > darianmiller
> > .com
> >
> > "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> > news:%23EMfUSHbFHA.720@.TK2MSFTNGP15.phx.gbl...
> >> Hi
> >>
> >> Darian, how busy was your SQL Server to have this problem?
> >>
> >> Regards
> >> --
> >> Mike Epprecht, Microsoft SQL Server MVP
> >> Zurich, Switzerland
> >>
> >> IM: mike@.epprecht.net
> >>
> >> MVP Program: http://www.microsoft.com/mvp
> >>
> >> Blog: http://www.msmvps.com/epprecht/
> >>
> >> "Darian Miller" <darianmiller@.online.nospam> wrote in message
> >> news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> >> > Note: watch out with Windows 2003 SP1 and a busy SQL Server...this
one
> >> > just
> >> > hit us pretty good:
> >> > http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
> >> >
> >> > Darian Miller
> >> >
> >> >
> >> > "Hassan" <fatima_ja@.hotmail.com> wrote in message
> >> > news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> >> >> Heard there are issues with AWE and Windows 2003 and SP1 for Windows
> >> >> fixes
> >> >> it. Does anyone know more or a KB article ?
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>|||So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> Here are a few:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;895575
> http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> > Heard there are issues with AWE and Windows 2003 and SP1 for Windows
fixes
> > it. Does anyone know more or a KB article ?
> >
> >
>|||Actually, a PAE fix for Win2K3 has also been released as part of a Security
Hotfix Critical Update:
Microsoft Security Bulletin MS04-032
Security Update for Microsoft Windows (840987)
http://www.microsoft.com/technet/security/bulletin/ms04-032.mspx
Sincerely,
Anthony Thomas
--
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> Here are a few:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;895575
> http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> > Heard there are issues with AWE and Windows 2003 and SP1 for Windows
fixes
> > it. Does anyone know more or a KB article ?
> >
> >
>|||The issues with w2k3 at very small compared to NT 4.0 and w2k.
We found that most of the 'issues' with w2k3 are NT 4.0 MCSE's not
understanding security.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
> So with all these issues with Win2K3, what does MS have to say ? Do
> companies move forward on Win2K3 ?
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
>> Here are a few:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;895575
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;838765
>> Adrian
>>
>> "Hassan" <fatima_ja@.hotmail.com> wrote in message
>> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>> > Heard there are issues with AWE and Windows 2003 and SP1 for Windows
> fixes
>> > it. Does anyone know more or a KB article ?
>> >
>> >
>>
>

Any known issues with AWE and Windows 2003

Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
it. Does anyone know more or a KB article ?
I am not sure, but we are currently experinceing performance issues
since going to SP1. See my post in this group, Too Much RAM SQL Server
2000?
|||Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one just
hit us pretty good:
http://support.microsoft.com/default...b;en-us;899599
Darian Miller
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>
|||Hi
Darian, how busy was your SQL Server to have this problem?
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Darian Miller" <darianmiller@.online.nospam> wrote in message
news:elshGJHbFHA.3848@.TK2MSFTNGP10.phx.gbl...
> Note: watch out with Windows 2003 SP1 and a busy SQL Server...this one
> just
> hit us pretty good:
> http://support.microsoft.com/default...b;en-us;899599
> Darian Miller
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
>
|||Here are a few:
http://support.microsoft.com/default...b;en-us;895575
http://support.microsoft.com/default...b;en-us;838765
Adrian
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
> Heard there are issues with AWE and Windows 2003 and SP1 for Windows fixes
> it. Does anyone know more or a KB article ?
>
|||So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...[vbcol=seagreen]
> Here are a few:
> http://support.microsoft.com/default...b;en-us;895575
> http://support.microsoft.com/default...b;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
fixes
>
|||Actually, a PAE fix for Win2K3 has also been released as part of a Security
Hotfix Critical Update:
Microsoft Security Bulletin MS04-032
Security Update for Microsoft Windows (840987)
http://www.microsoft.com/technet/sec.../ms04-032.mspx
Sincerely,
Anthony Thomas
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
So with all these issues with Win2K3, what does MS have to say ? Do
companies move forward on Win2K3 ?
"Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
news:MNednY37e_KSPTrfRVn-1A@.rogers.com...[vbcol=seagreen]
> Here are a few:
> http://support.microsoft.com/default...b;en-us;895575
> http://support.microsoft.com/default...b;en-us;838765
> Adrian
>
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:%23pWXnzFbFHA.1660@.tk2msftngp13.phx.gbl...
fixes
>
|||The issues with w2k3 at very small compared to NT 4.0 and w2k.
We found that most of the 'issues' with w2k3 are NT 4.0 MCSE's not
understanding security.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:OuOCc4VbFHA.2420@.TK2MSFTNGP15.phx.gbl...
> So with all these issues with Win2K3, what does MS have to say ? Do
> companies move forward on Win2K3 ?
> "Adrian Zajkeskovic" <azajkeskovic@.hotmail.com> wrote in message
> news:MNednY37e_KSPTrfRVn-1A@.rogers.com...
> fixes
>

Any Issues With Windows 2003 SP1?

Hi,
Does anybody know of any issues with Windows 2003 SP1?
We have a Standard SQL Server 2000 with SP3 running on Windows 2003.
Lee Aholima
DBA and IT Support
YES!
http://support.microsoft.com/default...b;en-us;899599
"dayfive" <dayfive@.discussions.microsoft.com> wrote in message
news:6FA46E11-7EB7-4EBC-9160-51411A87A8F3@.microsoft.com...
> Hi,
> Does anybody know of any issues with Windows 2003 SP1?
> We have a Standard SQL Server 2000 with SP3 running on Windows 2003.
> --
> Lee Aholima
> DBA and IT Support
>

Any Issues With Windows 2003 SP1?

Hi,
Does anybody know of any issues with Windows 2003 SP1?
We have a Standard SQL Server 2000 with SP3 running on Windows 2003.
Lee Aholima
DBA and IT SupportYES!
http://support.microsoft.com/defaul...kb;en-us;899599
"dayfive" <dayfive@.discussions.microsoft.com> wrote in message
news:6FA46E11-7EB7-4EBC-9160-51411A87A8F3@.microsoft.com...
> Hi,
> Does anybody know of any issues with Windows 2003 SP1?
> We have a Standard SQL Server 2000 with SP3 running on Windows 2003.
> --
> Lee Aholima
> DBA and IT Support
>

Any Issues With Windows 2003 SP1?

Hi,
Does anybody know of any issues with Windows 2003 SP1?
We have a Standard SQL Server 2000 with SP3 running on Windows 2003.
--
Lee Aholima
DBA and IT SupportYES!
http://support.microsoft.com/default.aspx?scid=kb;en-us;899599
"dayfive" <dayfive@.discussions.microsoft.com> wrote in message
news:6FA46E11-7EB7-4EBC-9160-51411A87A8F3@.microsoft.com...
> Hi,
> Does anybody know of any issues with Windows 2003 SP1?
> We have a Standard SQL Server 2000 with SP3 running on Windows 2003.
> --
> Lee Aholima
> DBA and IT Support
>

Any issues with Windows 2000 service pack 4 with sql server?

Does anyone know if there are known issues with SQL when
upgrading a windows 2000 server to service pack 4?Nothing specific that I have seen so far.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Jdent" <jdent@.shentel.net> wrote in message
news:01f201c3b38a$aed48d50$a401280a@.phx.gbl...
Does anyone know if there are known issues with SQL when
upgrading a windows 2000 server to service pack 4?

2012年2月23日星期四

Any improvements to this: Cannot apply value null to property Login: Value cannot be null.

Looks like there was a fix and then I read this fix is not a fix. Does anyone know how this can be rectified? Does it mean that only Windows authentiation is the only way it works. The Software is over 2 years old, there are no excuses.

Jayaram Krishnaswamy wrote:

Looks like there was a fix and then I read this fix is not a fix. Does anyone know how this can be rectified? Does it mean that only Windows authentiation is the only way it works. The Software is over 2 years old, there are no excuses.

Perhaps if you explained what on earth you're talking about someone could help. Explaining how you got this error would be a good place to start.

The software is 16 months old by the way.

-Jamie

2012年2月16日星期四

Any equivalent to Oracle RAC available for SQL Server?

Using Windows clustering requires too long a failover time for my company's
uptime requirements. While SQL 2005's mirroring decreases the failover
time, it also only allows me to mirror to one server, thus putting me in a
rough spot for DR.
Is there any Oracle RAC type equivalent functionality (i.e. shared cache)
planned for future versions of SQL 2005, or available via some 3rd party
today for use with SQL 2005 today? The net is, I need as little downtime as
possible, both within a site, and across to my DR site (and as little to no
data loss as possible to that DR site)...all the while (of course)
minimizing the perf hit all of this requires...though while perf needs to
still fall in acceptable ranges, better perf is not as important as faster
failover and no data loss.
Any help is appeciated.
Thanks
RAC is by no means a High Availability feature so I am confused as to the
subject. There is no SQL Server RAC equivalent in the current release for a
read write database. However there are several HA / DR features that SQL
Server has that people use every day to satisfy their HA / DR needs. How
fast the recovery and how little down time is usually more a factor of how
much money you wish to spend. For instance you can do mirroring to get fast
up time and use the SAN's features to do DR. This is just a simple example
and it will really depend on what you want, what you have to work with and
how much time and money youa re willing to put into it. You might want to
start here:
http://www.microsoft.com/sql/technologies/highavailability/default.mspx
Andrew J. Kelly SQL MVP
"Jim" <ilmm555@.yahoo.com> wrote in message
news:uimO$QJhHHA.4980@.TK2MSFTNGP02.phx.gbl...
> Using Windows clustering requires too long a failover time for my
> company's uptime requirements. While SQL 2005's mirroring decreases the
> failover time, it also only allows me to mirror to one server, thus
> putting me in a rough spot for DR.
> Is there any Oracle RAC type equivalent functionality (i.e. shared cache)
> planned for future versions of SQL 2005, or available via some 3rd party
> today for use with SQL 2005 today? The net is, I need as little downtime
> as possible, both within a site, and across to my DR site (and as little
> to no data loss as possible to that DR site)...all the while (of course)
> minimizing the perf hit all of this requires...though while perf needs to
> still fall in acceptable ranges, better perf is not as important as faster
> failover and no data loss.
> Any help is appeciated.
> Thanks
|||OK, while RAC's original intent is to be a scale out feature, it's also very
much an HA feature...as if a node dies, other nodes press on...there's no
notion of "failover", thus eliminating the need to failover.
I disagree with it being "a factor of how much money you wish to spend"...as
regardless of how much you spend, the best you'll get SQL to is seconds of
downtime (with mirroring, likely 10s of seconds-minutes with
clustering)...thus, if you were to patch once a month (between SQL and
Windows this is certainly not out of the realm of possibility), that's
twelve failovers per year, at (at best...10 seconds of downtime each
failover)...so you're at 120 seconds a year...99.999% availability is 52.256
seconds...so you're already down to under 5 9's availability for the year.
In this shop, there's no notion of "unplanned downtime"...we're 24x7...it's
ALL downtime.
As for mirroring with SAN replicaiton for DR...below I mention no data loss,
so you'd be talking about synchronous mirroing WITH synchronous SAN
replication...while I said perf isn't the highest priority...I wonder how
slow it would be with effectively 3 writes for each write (one to the
primary SQL, one to the secondary SQL, one to the DR site...and since this
is all synchronous...all writes have to be completed before the
transaction's commited)...plus, now you're using SQL failover functionality
and SAN failover functionality...I certainly wonder how (operationally)
feasible this all will be...I'm sure it will be feasible, but certainly not
seamless...
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uPErZcShHHA.4064@.TK2MSFTNGP02.phx.gbl...
> RAC is by no means a High Availability feature so I am confused as to the
> subject. There is no SQL Server RAC equivalent in the current release for
> a read write database. However there are several HA / DR features that SQL
> Server has that people use every day to satisfy their HA / DR needs. How
> fast the recovery and how little down time is usually more a factor of how
> much money you wish to spend. For instance you can do mirroring to get
> fast up time and use the SAN's features to do DR. This is just a simple
> example and it will really depend on what you want, what you have to work
> with and how much time and money youa re willing to put into it. You might
> want to start here:
> http://www.microsoft.com/sql/technologies/highavailability/default.mspx
>
> --
> Andrew J. Kelly SQL MVP
> "Jim" <ilmm555@.yahoo.com> wrote in message
> news:uimO$QJhHHA.4980@.TK2MSFTNGP02.phx.gbl...
>
|||While RAC does give some flexibility in terms of a single node failure there
are still plenty of places that are close to single point of failure without
additional effort. And it does nothing for DR. Oracle or anyother rdbms has
no magic solution to guarantee 0 down time. It really boils down to the
limitations of hardware. You are not the 1st company looking for 24X7
operation. Hundreds if not thousands of companies use SQL Server every day
for 5 nines of availability. I disagree with the down time for the number
of patches. How often you patch is often up to you. I had a system running
for almost 3 years. It was secure and did what we wanted so we choose not to
patch it.
Andrew J. Kelly SQL MVP
"Jim" <ilmm555@.yahoo.com> wrote in message
news:eMz1vgVhHHA.1388@.TK2MSFTNGP05.phx.gbl...
> OK, while RAC's original intent is to be a scale out feature, it's also
> very much an HA feature...as if a node dies, other nodes press
> on...there's no notion of "failover", thus eliminating the need to
> failover.
> I disagree with it being "a factor of how much money you wish to
> spend"...as regardless of how much you spend, the best you'll get SQL to
> is seconds of downtime (with mirroring, likely 10s of seconds-minutes with
> clustering)...thus, if you were to patch once a month (between SQL and
> Windows this is certainly not out of the realm of possibility), that's
> twelve failovers per year, at (at best...10 seconds of downtime each
> failover)...so you're at 120 seconds a year...99.999% availability is
> 52.256 seconds...so you're already down to under 5 9's availability for
> the year. In this shop, there's no notion of "unplanned downtime"...we're
> 24x7...it's ALL downtime.
> As for mirroring with SAN replicaiton for DR...below I mention no data
> loss, so you'd be talking about synchronous mirroing WITH synchronous SAN
> replication...while I said perf isn't the highest priority...I wonder how
> slow it would be with effectively 3 writes for each write (one to the
> primary SQL, one to the secondary SQL, one to the DR site...and since this
> is all synchronous...all writes have to be completed before the
> transaction's commited)...plus, now you're using SQL failover
> functionality and SAN failover functionality...I certainly wonder how
> (operationally) feasible this all will be...I'm sure it will be feasible,
> but certainly not seamless...
>
> "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
> news:uPErZcShHHA.4064@.TK2MSFTNGP02.phx.gbl...
>
|||Hello Jim,
I am interested you say that SQL clustering is to slow. I run 8 production
clusters of various sizes, one is 300 GB just for data and fail over takes
about 30 seconds. Is 30 seconds to slow? If so then using a database mirror
would be the way to go. You will need to ensure that the client is using
ADO.NET 2.0 so that your failover is supported. However, there will be no
need to handle the failover as there is when using TAF on RAC.
Having said that currently SQL server has no RAC equivalency for scaling
out. If this is a requirement I would go with a HP Itanium system such as
the 6840 this would allow you to scale up over time rather than scaling out.
Let me know if you need clarification
John Vandervliet.
"Jim" <ilmm555@.yahoo.com> wrote in message
news:uimO$QJhHHA.4980@.TK2MSFTNGP02.phx.gbl...
> Using Windows clustering requires too long a failover time for my
> company's uptime requirements. While SQL 2005's mirroring decreases the
> failover time, it also only allows me to mirror to one server, thus
> putting me in a rough spot for DR.
> Is there any Oracle RAC type equivalent functionality (i.e. shared cache)
> planned for future versions of SQL 2005, or available via some 3rd party
> today for use with SQL 2005 today? The net is, I need as little downtime
> as possible, both within a site, and across to my DR site (and as little
> to no data loss as possible to that DR site)...all the while (of course)
> minimizing the perf hit all of this requires...though while perf needs to
> still fall in acceptable ranges, better perf is not as important as faster
> failover and no data loss.
> Any help is appeciated.
> Thanks
|||Do you run 8 production clusters where all of them are single instance
cluster..i.e one active and one passive or do you have a multi instance
cluster say more than 2 active nodes with 1 passive node for any of the
active nodes to failover.
"John Vandervliet" <jvandervliet@.SJRB.AD> wrote in message
news:7FE2AB87-4B70-44A0-8400-85B209FC6626@.microsoft.com...
> Hello Jim,
> I am interested you say that SQL clustering is to slow. I run 8 production
> clusters of various sizes, one is 300 GB just for data and fail over takes
> about 30 seconds. Is 30 seconds to slow? If so then using a database
> mirror would be the way to go. You will need to ensure that the client is
> using ADO.NET 2.0 so that your failover is supported. However, there will
> be no need to handle the failover as there is when using TAF on RAC.
> Having said that currently SQL server has no RAC equivalency for scaling
> out. If this is a requirement I would go with a HP Itanium system such as
> the 6840 this would allow you to scale up over time rather than scaling
> out.
> Let me know if you need clarification
> John Vandervliet.
>
> "Jim" <ilmm555@.yahoo.com> wrote in message
> news:uimO$QJhHHA.4980@.TK2MSFTNGP02.phx.gbl...
>
|||We run a combination most the instances are active/passive setups, howerver
we have 3 clusters that each of 2 instances of SQL. the servers are exact
matches of each other and can handle the load for both instances when needed.
"Hassan" wrote:

> Do you run 8 production clusters where all of them are single instance
> cluster..i.e one active and one passive or do you have a multi instance
> cluster say more than 2 active nodes with 1 passive node for any of the
> active nodes to failover.
>
> "John Vandervliet" <jvandervliet@.SJRB.AD> wrote in message
> news:7FE2AB87-4B70-44A0-8400-85B209FC6626@.microsoft.com...
>
>
|||On Apr 26, 5:12 pm, John Vandervliet
<JohnVandervl...@.discussions.microsoft.com> wrote:
> We run a combination most the instances are active/passive setups, howerver
> we have 3 clusters that each of 2 instances of SQL. the servers are exact
> matches of each other and can handle the load for both instances when needed.
>
> "Hassan" wrote:
>
>
>
>
>
> - Show quoted text -
Hassan,
My employer SteelEye Technology has a solution called LifeKeeper for
SQL Server. With our solution we can cluster 2-nodes locally with
either shared storage or syncronous host based replication and also
support a 3rd node in the DR site with either sync or async
replication. Of course sync replication will impact performance if
done across a WAN, but it is the only way to guarantee no data loss.
Failover time is similar to MSCS, so if that is too long, you will
have to look elsewhere.
Here is some information.
www.steeleye.com/pdf/literature/lifekeeper_for_sql_server.pdf
David A. Bermingham, MCSE, MCSA:Messaging
Director of Product Management
www.steeleye.com

Any Distributed Data failure

Scenario:
I have one windows server 2003 and 2 windows XP clients on one machine by virtual pc.
All pings to each other.
The 2 windows XP clients are joining a domain in the server.
They have administrator accounts and administrative privilages on each other.

On each windows there is SQL2000 with SP3 using windows authentication.
Each MSSQLServer and other SQL Services log in by the administrator domain account and has the domain account of the other windows in sysadmin role.

Both XP SQL Servers are linked to each other.

MSDTC is running on all servers with allowing every available option by Services Components.

Firewalls are off in all servers.

Although, neither distributed transactions work giving this error:
"Server: Msg 7391, Level 16, State 1, Line 7
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction."

Also Snapshot agent in replication cannot start.

My Question is: Is there something to do with RPC and how?
Please help...

Thanks.I found the answer in:
http://support.microsoft.com/kb/841251

Thanks

2012年2月13日星期一

Any books that explain how to setup Windows 2003 Server + SQL Server 2000?

My uncle runs a small networking company and has extra licenses for Windows 2003 Server as well as SQL Server 2000. Since I just graduated from college and have started working as a database programmer (for a different company) I'd like to setup a small server at home to learn more about SQL (as well as networking, but SQL is my primary concern). I know I can setup SQL Server 2000 on my main PC, but I'd still like to set everything up in a server environment.

So, what I'm wondering is if any books (or web sites?) exist that walk you through setting up Windows 2003 Server and SQL Server 2000. I've actually set these up before (it's not very complicated) but I'm not sure if I did it the "correct" way.

Ideally if any books exist on O'Reilly's Safari Bookshelf that would be even better.

Thanks in advance,
John1. install windows 2003.
2. install sql 2000. ignor warning.
3. install sql 2000 sp3.

your done.|||double post delete|||Thanks for the reply!

The service pack (3a is most recent I believe) gets a little confusing because there are three parts:

Sql2ksp3.exe. Updates for database components.
Sql2kasp3.exe. Updates for Analysis Services components.
Sql2kdesksp3.exe. Updates for Microsoft SQL Server 2000 Desktop Engine (MSDE 2000).

Do I need to install all three parts of the service pack?

Anything else I need to do?

Thanks,
John|||You just need to update the database components. I usually get rid of the sample data (northwind and pubs) when I do a new install but since you're testing you might as well play with those.

AntiVirus Software on SQL Server?

As a DBA, I was taught that running Anti-virus software on a database server
was not a very good thing to do. My network admin is planning a Windows 2000
migration and would like all machines across the domain to run AV software.
Can anyone tell me about their experience running AV software on their
database server, and whether this is a good idea or not.
The box runs SQL 6.5sp5a (soon to be 2k) and does not touch the outside
world at all.
Thanks for your help,
CurtisAs much as you may want to keep anti-virus software away
from a SQL box, you'll soon realize that that's a lost
battle. When there is a virus crisis, whatever arguments
you may have to avoid anti-virus on your SQL box, you'll
end being defeated badly.
My experience is to simply give up on avoiding virus scan
completely, and ask for the SQL files being excluded from
the virus scan. I typically ask the security folks to
exclude the following files from being scanned: *.MDF,
*.LDF, *.NDF, *.BAK, *.TRN, and *.BKP.
The primary reason you don't want anti-virus scanning is
that the virus scan software may get hold of a SQL
data/log file and prevents SQL Server from opening it,
resulting in the database being put into the suspect mode.
Usually, these data/log files are open all the time, and
therefore not an issue. But sometimes we may need to shut
down SQL Server instance or detach a database. Before we
restart SQL Server or attach the database, if the virus
software gets ahead of us, we are screwed.
There are also some issues with SQL Server running in a
cluster.
Check out: Q309422 and Q250355
Linchi
>--Original Message--
>As a DBA, I was taught that running Anti-virus software
on a database server
>was not a very good thing to do. My network admin is
planning a Windows 2000
>migration and would like all machines across the domain
to run AV software.
>Can anyone tell me about their experience running AV
software on their
>database server, and whether this is a good idea or not.
>The box runs SQL 6.5sp5a (soon to be 2k) and does not
touch the outside
>world at all.
>Thanks for your help,
>Curtis
>
>.
>

Antivirus software on SQL Server 2000

I am preparing to install SQL Server 2000 on a Windows 2003 server. There will be no file or print sharing services or in general no other processes running on this server except those required by SQL Server. The SQL Server is behind a filewall and will only be accessed internally. Should I install McAfee or Norton antivirus software on this machine? If so, are there any special configuration options that I should consider?Check out this KB article.
INF: Consideration for a Virus Scanner on a Computer That Is Running SQL
Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;309422&Product=sql2k
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
"Lane Lesperance" <LLesperance@.cooperpower.com> wrote in message
news:ekCZHsCwDHA.1764@.TK2MSFTNGP10.phx.gbl...
> I am preparing to install SQL Server 2000 on a Windows 2003 server. There
will be no file or print sharing services or in general no other processes
running on this server except those required by SQL Server. The SQL Server
is behind a filewall and will only be accessed internally. Should I install
McAfee or Norton antivirus software on this machine? If so, are there any
special configuration options that I should consider?
>|||See http://support.microsoft.com/default.aspx?scid=kb;en-
us;309422
In general, it is not recommended to do so if you don't
have to on a SQL box due to the things you mention (i.e.
not a file server, etc.). If you do, filter the SQL
DB/log files (not the executables), and if it's a cluster,
filter the \MSCS and if it exists, \MSDtc folders on the
quorum.
>--Original Message--
>I am preparing to install SQL Server 2000 on a Windows
2003 server. There will be no file or print sharing
services or in general no other processes running on this
server except those required by SQL Server. The SQL Server
is behind a filewall and will only be accessed internally.
Should I install McAfee or Norton antivirus software on
this machine? If so, are there any special configuration
options that I should consider?
>
>.
>