Sql ANSI Padding: sp1

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

2012年3月8日星期四

Any scripts that will create maintenance plans in SQL 2005

Hi
Using SQL Server 2005 SP1
Are ther any way to create scripts that will recreate the maintenance plans
that are on the server?
We need to rebuild the server with a different collation, so the master,
msdb and model will get recreated.
Also where are the configurations for database mail kept. No scripts to
create them.
Any place that has scripts that can regenerate the data that one requires?
ThanksYou can connect Object Explorer to Integration Services and Export the maint plan to a file. After
the rebuild, import that file, and just re-create the jobs (or script the Agent jobs as well...).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Raji Arulambalam" <rajian0spam@.ebop.gov0t.nz> wrote in message
news:O7P4Kd44GHA.4616@.TK2MSFTNGP05.phx.gbl...
> Hi
> Using SQL Server 2005 SP1
> Are ther any way to create scripts that will recreate the maintenance plans that are on the
> server?
> We need to rebuild the server with a different collation, so the master, msdb and model will get
> recreated.
> Also where are the configurations for database mail kept. No scripts to create them.
> Any place that has scripts that can regenerate the data that one requires?
> Thanks
>

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/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

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 2005 SP1?

Does anyone know of any major, or indeed minor, issues with installing SP1
for SQL 2005?
Michael MacGregor
Database ArchitectThere were some installation issues.
http://www.google.com/search?source...k+1+ssis+failed
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Michael MacGregor" <nospam@.nospam.com> wrote in message
news:e4KLsm10GHA.3900@.TK2MSFTNGP05.phx.gbl...
> Does anyone know of any major, or indeed minor, issues with installing SP1
> for SQL 2005?
> Michael MacGregor
> Database Architect
>|||If I remember correctly there was something about SSIS not starting
after applying SP1
http://connect.microsoft.com/SQLSer...=12530
6
and this one
SP1 breaks SSIS Packages with date variables due to dates being now
interpreted as mmddyyyy rather than ddmmyyyy
http://connect.microsoft.com/SQLSer...=12467
5
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Michael MacGregor wrote:
> Does anyone know of any major, or indeed minor, issues with installing SP1
> for SQL 2005?
> Michael MacGregor
> Database Architect|||Michael,
Is this on a cluster or standalone server?
Chris
"Michael MacGregor" <nospam@.nospam.com> wrote in message
news:e4KLsm10GHA.3900@.TK2MSFTNGP05.phx.gbl...
> Does anyone know of any major, or indeed minor, issues with installing SP1
> for SQL 2005?
> Michael MacGregor
> Database Architect
>|||The production machine is a cluster, but we have other servers that are not.
Michael MacGregor
Database Architect
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:O3Ay$d20GHA.4044@.TK2MSFTNGP04.phx.gbl...
> Michael,
> Is this on a cluster or standalone server?
> Chris
> "Michael MacGregor" <nospam@.nospam.com> wrote in message
> news:e4KLsm10GHA.3900@.TK2MSFTNGP05.phx.gbl...
>

Any issues with 2005 SP1?

Does anyone know of any major, or indeed minor, issues with installing SP1
for SQL 2005?
Michael MacGregor
Database ArchitectThere were some installation issues.
http://www.google.com/search?sourceid=navclient&ie=UTF-8&rls=GGLG,GGLG:2006-07,GGLG:en&q=sql+service+pack+1+ssis+failed
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Michael MacGregor" <nospam@.nospam.com> wrote in message
news:e4KLsm10GHA.3900@.TK2MSFTNGP05.phx.gbl...
> Does anyone know of any major, or indeed minor, issues with installing SP1
> for SQL 2005?
> Michael MacGregor
> Database Architect
>|||If I remember correctly there was something about SSIS not starting
after applying SP1
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125306
and this one
SP1 breaks SSIS Packages with date variables due to dates being now
interpreted as mmddyyyy rather than ddmmyyyy
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124675
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Michael MacGregor wrote:
> Does anyone know of any major, or indeed minor, issues with installing SP1
> for SQL 2005?
> Michael MacGregor
> Database Architect|||Michael,
Is this on a cluster or standalone server?
Chris
"Michael MacGregor" <nospam@.nospam.com> wrote in message
news:e4KLsm10GHA.3900@.TK2MSFTNGP05.phx.gbl...
> Does anyone know of any major, or indeed minor, issues with installing SP1
> for SQL 2005?
> Michael MacGregor
> Database Architect
>|||The production machine is a cluster, but we have other servers that are not.
Michael MacGregor
Database Architect
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:O3Ay$d20GHA.4044@.TK2MSFTNGP04.phx.gbl...
> Michael,
> Is this on a cluster or standalone server?
> Chris
> "Michael MacGregor" <nospam@.nospam.com> wrote in message
> news:e4KLsm10GHA.3900@.TK2MSFTNGP05.phx.gbl...
>> Does anyone know of any major, or indeed minor, issues with installing
>> SP1 for SQL 2005?
>> Michael MacGregor
>> Database Architect
>

2012年2月23日星期四

Any issues with 2005 SP1?

Does anyone know of any major, or indeed minor, issues with installing SP1
for SQL 2005?
Michael MacGregor
Database ArchitectThere were some installation issues.
http://www.google.com/search?sourceid=navclient&ie=UTF-8&rls=GGLG,GGLG:2006-07,GGLG:en&q=sql+service+pack+1+ssis+failed
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Michael MacGregor" <nospam@.nospam.com> wrote in message
news:e4KLsm10GHA.3900@.TK2MSFTNGP05.phx.gbl...
> Does anyone know of any major, or indeed minor, issues with installing SP1
> for SQL 2005?
> Michael MacGregor
> Database Architect
>|||If I remember correctly there was something about SSIS not starting
after applying SP1
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125306
and this one
SP1 breaks SSIS Packages with date variables due to dates being now
interpreted as mmddyyyy rather than ddmmyyyy
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=124675
Denis the SQL Menace
http://sqlservercode.blogspot.com/
Michael MacGregor wrote:
> Does anyone know of any major, or indeed minor, issues with installing SP1
> for SQL 2005?
> Michael MacGregor
> Database Architect|||Michael,
Is this on a cluster or standalone server?
Chris
"Michael MacGregor" <nospam@.nospam.com> wrote in message
news:e4KLsm10GHA.3900@.TK2MSFTNGP05.phx.gbl...
> Does anyone know of any major, or indeed minor, issues with installing SP1
> for SQL 2005?
> Michael MacGregor
> Database Architect
>|||The production machine is a cluster, but we have other servers that are not.
Michael MacGregor
Database Architect
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:O3Ay$d20GHA.4044@.TK2MSFTNGP04.phx.gbl...
> Michael,
> Is this on a cluster or standalone server?
> Chris
> "Michael MacGregor" <nospam@.nospam.com> wrote in message
> news:e4KLsm10GHA.3900@.TK2MSFTNGP05.phx.gbl...
>> Does anyone know of any major, or indeed minor, issues with installing
>> SP1 for SQL 2005?
>> Michael MacGregor
>> Database Architect
>

2012年2月11日星期六

anti-virus on sql server box?

hi!

i am using sql 2005 with sp1 standard edition.

i have a question regarding the antivirus software. Is it ok to install anti-virus software on the sql server box? what are the issues involved if we install anti-virus software on the sql server box?
I heard, it causes some performance and other issues.

Is there anything we need to take care of .if we decide to install anti-virus software on the sql server box?

Can anybody share experience on this?

Thanks

Personally, I am very much against installing anti-virus software on a SQL Server box, for performance reasons. You see conflicting advice from Microsoft about this. The Perf people say no, and the security people say yes. If you decide to run AV on your SQL Server, make sure to exclude the data and log files from the scanning.|||

Generally speaking, it is not a good idea to have anti-virus products on a SQL Server.

Consider that anti-virus products protect the computer from user activities in the Workstation service.

On a SQL Server, there 'should' not be any user activities in the Workstation service.

|||I disagree with the other posts here.

ALWAYS run anti-virus on ALL machines on the network, servers and pcs, with current virus defs.

On SQL server, exclude the data and log directories from the scanning and virus protection.

Many viruses will infect all machines on the entire network, and if you don't have AV on ALL machines, when you remove it from all your PCs, it will hide on your SQL server box until it infects the entire network again and again and again. I know because this has happened to me, with more than one customer who has the same "performance" concerns.
|||Yes, I agree with Tlom. There are several approaches, defined by the policy of the companies which way you can take if you secure SQL Server. You can either exclude the data file and directories or exclude the appropuiate MDF / LDF extensions (which assumes that you are using these extensions with your files) I prefer the extensions exclusion which will makes it even not possible to inject a virus in the data directories of SQL Server.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Thank you everyone for your replies. I really appreciate it.

So if you exclude the data and log files, are there any performance issues and other issues like communication/blocking etc ?

Thanks
|||

I hope this will help you:

Guidelines for choosing antivirus software to run on the computers that are running SQL Server

http://support.microsoft.com/kb/309422/en-us

ANSI_NULLS OFF SQL2K5

Hi folks,
I'm using SQL Server 2005 SP1 and wants to know how to set to OFF the
setting ANSI_NULLS. When I create or modify a SP, SQL Server 2005 proposes
automatically the settings (global)
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
When I modify the SP cliccking on "Script store procedure as" and then
"ALTER TO" to change the setting ANSI_NULLS to OFF, it remains in OFF. The
problem is when I modify the SP cliccking on "Modify"; if the SP was modified
first changing the ANSI_NULLS setting to OFF, SSMS continues to visualize
such setting in ON. Very weird!
Any insight about how to preserve such setting in OFF is really welcome.
Thanks. Roberto.BOBNET wrote:
> Hi folks,
> I'm using SQL Server 2005 SP1 and wants to know how to set to OFF the
> setting ANSI_NULLS. When I create or modify a SP, SQL Server 2005 proposes
> automatically the settings (global)
> SET ANSI_NULLS ON
> SET QUOTED_IDENTIFIER ON
> When I modify the SP cliccking on "Script store procedure as" and then
> "ALTER TO" to change the setting ANSI_NULLS to OFF, it remains in OFF. The
> problem is when I modify the SP cliccking on "Modify"; if the SP was modified
> first changing the ANSI_NULLS setting to OFF, SSMS continues to visualize
> such setting in ON. Very weird!
> Any insight about how to preserve such setting in OFF is really welcome.
> Thanks. Roberto.
If at all possible you should avoid setting ANSI_NULLS OFF. Use the ON
setting always. The only good reason I can think of to use the OFF
setting is in order to support legacy code that you can't change. If
you do use the OFF setting then some features are not supported and
worst of all your code will be harder for others to comprehend.
Set ANSI_NULLS in the script just before the CREATE PROC statement:
SET ANSI_NULLS OFF
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE PROC [dbo].[usp_proc]
...
You can also set Management Studio's default behaviour under Options /
Query Execution\SQL Server\ANSI. Changing this to OFF is definitely not
recommended because it will affect ALL new procs unless you remember to
specify otherwise.
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

ANSI_NULLS OFF SQL2K5

Hi folks,
I'm using SQL Server 2005 SP1 and wants to know how to set to OFF the
setting ANSI_NULLS. When I create or modify a SP, SQL Server 2005 proposes
automatically the settings (global)
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
When I modify the SP cliccking on "Script store procedure as" and then
"ALTER TO" to change the setting ANSI_NULLS to OFF, it remains in OFF. The
problem is when I modify the SP cliccking on "Modify"; if the SP was modifie
d
first changing the ANSI_NULLS setting to OFF, SSMS continues to visualize
such setting in ON. Very weird!
Any insight about how to preserve such setting in OFF is really welcome.
Thanks. Roberto.BOBNET wrote:
> Hi folks,
> I'm using SQL Server 2005 SP1 and wants to know how to set to OFF the
> setting ANSI_NULLS. When I create or modify a SP, SQL Server 2005 proposes
> automatically the settings (global)
> SET ANSI_NULLS ON
> SET QUOTED_IDENTIFIER ON
> When I modify the SP cliccking on "Script store procedure as" and then
> "ALTER TO" to change the setting ANSI_NULLS to OFF, it remains in OFF. The
> problem is when I modify the SP cliccking on "Modify"; if the SP was modif
ied
> first changing the ANSI_NULLS setting to OFF, SSMS continues to visualize
> such setting in ON. Very weird!
> Any insight about how to preserve such setting in OFF is really welcome.
> Thanks. Roberto.
If at all possible you should avoid setting ANSI_NULLS OFF. Use the ON
setting always. The only good reason I can think of to use the OFF
setting is in order to support legacy code that you can't change. If
you do use the OFF setting then some features are not supported and
worst of all your code will be harder for others to comprehend.
Set ANSI_NULLS in the script just before the CREATE PROC statement:
SET ANSI_NULLS OFF
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE PROC [dbo].[usp_proc]
...
You can also set Management Studio's default behaviour under Options /
Query Execution\SQL Server\ANSI. Changing this to OFF is definitely not
recommended because it will affect ALL new procs unless you remember to
specify otherwise.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

订阅：博文 (Atom)

2012年3月8日星期四

Any scripts that will create maintenance plans in SQL 2005

2012年2月25日星期六

Any known issues with AWE and Windows 2003

Any known issues with AWE and Windows 2003

Any known issues with AWE and Windows 2003

Any Issues With Windows 2003 SP1?

Any Issues With Windows 2003 SP1?

Any Issues With Windows 2003 SP1?

Any issues with 2005 SP1?

Any issues with 2005 SP1?

2012年2月23日星期四

Any issues with 2005 SP1?

2012年2月11日星期六

anti-virus on sql server box?

ANSI_NULLS OFF SQL2K5

ANSI_NULLS OFF SQL2K5

Sql ANSI Padding

Blog Archive

About Me