Sql ANSI Padding: regarding

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

2012年2月18日星期六

Any Help regarding SQL Reporting Services

Hi,
I checked with msdn for help in sql Reporting Services.
Where can i find help for the same.
--
SushiLIf I understand you correctly you are asking where the documentation is?
When you install RS it installs Books OnLine. That is where all the
documentation is located.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Sushil" <Sushil@.discussions.microsoft.com> wrote in message
news:D3072889-4C65-4EAC-A4C5-9AF7FF37A58A@.microsoft.com...
> Hi,
> I checked with msdn for help in sql Reporting Services.
> Where can i find help for the same.
> --
> SushiL|||Thanks a lot Bruce but i'm not able to find it. Is there any other way if i
can find the documentation. It would be a great help if you tell b'coz i have
already installed Reporting Services. i checked it in MSDN.Net as well as
book online of SQL Server but im not able to find it.
--
SushiL
"Bruce L-C [MVP]" wrote:
> If I understand you correctly you are asking where the documentation is?
> When you install RS it installs Books OnLine. That is where all the
> documentation is located.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Sushil" <Sushil@.discussions.microsoft.com> wrote in message
> news:D3072889-4C65-4EAC-A4C5-9AF7FF37A58A@.microsoft.com...
> > Hi,
> >
> > I checked with msdn for help in sql Reporting Services.
> > Where can i find help for the same.
> > --
> > SushiL
>
>|||Reporting Services BOL is found by going to program manager -> sql server ->
reporting services (note the exact naming might be different, I am on a
computer without RS installed). So, you should have the reporting services
showing up, what happens when you go there. If you don't then you need to
reinstall. Did you install the client tools? I have BOL regardless. Both on
my servers and on my development machine.
You could also try this (installing an updated version of BOL).
http://www.microsoft.com/downloads/details.aspx?FamilyID=5e550d73-8f35-435e-bb71-c8573a1cdbdb&DisplayLang=en
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Sushil" <Sushil@.discussions.microsoft.com> wrote in message
news:B2A50B72-652C-40A5-9B05-FAB98E53BE52@.microsoft.com...
> Thanks a lot Bruce but i'm not able to find it. Is there any other way if
> i
> can find the documentation. It would be a great help if you tell b'coz i
> have
> already installed Reporting Services. i checked it in MSDN.Net as well as
> book online of SQL Server but im not able to find it.
> --
> SushiL
>
> "Bruce L-C [MVP]" wrote:
>> If I understand you correctly you are asking where the documentation is?
>> When you install RS it installs Books OnLine. That is where all the
>> documentation is located.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Sushil" <Sushil@.discussions.microsoft.com> wrote in message
>> news:D3072889-4C65-4EAC-A4C5-9AF7FF37A58A@.microsoft.com...
>> > Hi,
>> >
>> > I checked with msdn for help in sql Reporting Services.
>> > Where can i find help for the same.
>> > --
>> > SushiL
>>

2012年2月13日星期一

Any book on SQL

Hi,
I am lookig for some good booktitles for improving query building
capabilities. Any one has any suggestion regarding book or any other materia
l
please reply.
NilkanthThe Guru's Guide to Transact-SQL
by Ken Henderson
http://www.amazon.com/exec/obidos/A...link%5Fcode=xm2
Professional SQL Server 2000 Programming
by Robert Vieira
http://www.amazon.com/exec/obidos/A...link%5Fcode=xm2
Inside Microsoft SQL Server 2000
by Kalen Delaney
http://www.amazon.com/exec/obidos/A...link%5Fcode=xm2
Microsoft SQL Server 2000 Unleashed (2nd Edition)
by Ray Rankins, Paul Jensen, Paul Bertucci
http://www.amazon.com/exec/obidos/A...link%5Fcode=xm2
The Guru's Guide to SQL Server Stored Procedures, XML, and HTML
by Ken Henderson
http://www.amazon.com/exec/obidos/A...link%5Fcode=xm2
By the way these are all T_SQL specific books, if you are looking for ANSI
SQL get one of Joe Celko's SQL books
Joe Celko's SQL for Smarties
http://www.amazon.com/exec/obidos/A...link%5Fcode=xm2
If you are a complete beginnner this is a good book
SQL Queries for Mere Mortals: A Hands-On Guide to Data Manipulation in SQL
by Michael J. Hernandez, John L. Viescas
http://www.amazon.com/exec/obidos/A...65
67355
That should do it
http://sqlservercode.blogspot.com/
"Nilkanth Desai" wrote:

> Hi,
> I am lookig for some good booktitles for improving query building
> capabilities. Any one has any suggestion regarding book or any other mater
ial
> please reply.
> Nilkanth|||Refer this also
http://vyaskn.tripod.com/sqlbooks.htm
Madhivanan|||Advanced Transact-SQL for SQL Server 2000
<http://www.amazon.com/exec/obidos/t...=books&n=507846>
by Itzik Ben-Gan & Tom Moreau is also an excellent book. And while
Inside Microsoft SQL Server 2000
<http://www.amazon.com/exec/obidos/t...711117?v=glance>
(Delaney) is perhaps the best book in its class (or perhaps tied with
Ken Henderson's Guru's Guide
<http://www.amazon.com/exec/obidos/t...g=UTF8&v=glance> ),
it's not really a "teach yourself T-SQL" type book but rather a "learn
everything there is to know about _SQL Server internals_".
Also, I came across this Amazon booklist by Fernando Guerrero
<http://www.solidqualitylearning.com...spx?source=S_FG> (SQL MVP &
one of the main SQL dudes at Solid Quality Learning) as I was looking up
the Amazon reference for Itzik & Tom's book:
Essential SQL Server Books
<http://www.amazon.com/exec/obidos/t...8387021-1711117>
*mike hodgson*
blog: http://sqlnerd.blogspot.com
SQL wrote:
>The Guru's Guide to Transact-SQL
>by Ken Henderson
>http://www.amazon.com/exec/obidos/A...link%5Fcode=xm2
>Professional SQL Server 2000 Programming
>by Robert Vieira
>http://www.amazon.com/exec/obidos/A...link%5Fcode=xm2
>Inside Microsoft SQL Server 2000
>by Kalen Delaney
>http://www.amazon.com/exec/obidos/A...link%5Fcode=xm2
>Microsoft SQL Server 2000 Unleashed (2nd Edition)
>by Ray Rankins, Paul Jensen, Paul Bertucci
>http://www.amazon.com/exec/obidos/A...link%5Fcode=xm2
>The Guru's Guide to SQL Server Stored Procedures, XML, and HTML
>by Ken Henderson
>http://www.amazon.com/exec/obidos/A...link%5Fcode=xm2
>By the way these are all T_SQL specific books, if you are looking for ANSI
>SQL get one of Joe Celko's SQL books
>Joe Celko's SQL for Smarties
>http://www.amazon.com/exec/obidos/A...link%5Fcode=xm2
>
>If you are a complete beginnner this is a good book
>SQL Queries for Mere Mortals: A Hands-On Guide to Data Manipulation in SQL
>by Michael J. Hernandez, John L. Viescas
>http://www.amazon.com/exec/obidos/A...6
567355
>
>That should do it
>http://sqlservercode.blogspot.com/
>
>"Nilkanth Desai" wrote:
>
>

any article regarding differences between SQL2K and Yukon

any article regarding differences between SQL2K and YukonThere is almost none public info on Yukon yet, as those who has access to it are under
non-disclosure agreements. Your best bet it probably to search the net and try to find out what has
"leaked" until now.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Hassan" <fatima_ja@.hotmail.com> wrote in message news:upjwehGgDHA.944@.TK2MSFTNGP11.phx.gbl...
>|||Of the information that has been made public, the biggest change appears to
be the ability to write stored procs, UDF's and triggers using any .NET
language. This could potentially alter, drastically, how coding is done at
the database level. T-SQL is also being beefed up significantly.
J.R.
Largo SQL Tools
The Finest Collection of SQL Tools Available
http://www.largosqltools.com
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:upjwehGgDHA.944@.TK2MSFTNGP11.phx.gbl...
>|||> language. This could potentially alter, drastically, how coding is done
at
> the database level.
I guess the key is 'could potentially'. Some other DBMSs have introduced
similar features. As far as I can tell from working with DBAs of those
products, the database level coding doesn't seem to have been altered that
drastically. Perhaps, it's just the DBA crowd I hang out with :-)
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Largo SQL Tools" <nospam@.yahoo.com> wrote in message
news:u0jRvfHgDHA.3616@.TK2MSFTNGP11.phx.gbl...
> Of the information that has been made public, the biggest change appears
to
> be the ability to write stored procs, UDF's and triggers using any .NET
> language. This could potentially alter, drastically, how coding is done
at
> the database level. T-SQL is also being beefed up significantly.
> J.R.
> Largo SQL Tools
> The Finest Collection of SQL Tools Available
> http://www.largosqltools.com
> "Hassan" <fatima_ja@.hotmail.com> wrote in message
> news:upjwehGgDHA.944@.TK2MSFTNGP11.phx.gbl...
> >
> >
>

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_PADDING Deprecated

I have a few questions regarding the ANSI_PADDING option. I see, according
to MSDN (http://msdn2.microsoft.com/en-us/library/ms187403.aspx), that this
option is deprecated:
> This feature will be removed in a future version of Microsoft SQL
> Server. Avoid using this feature in new development work, and
> plan to modify applications that currently use this feature.
My questions are:
1) What will this setting be fixed to once it is no longer supported?
According to MSDN, their recommendation is that we always have it set to ON,
and it states the default value is also ON. So I would assume that it will
be fixed to ON once it is no longer supported, but I don't see this
explicitly stated anywhere.
2) What will happen to existing databases with columns defined with this
option turned on? Will they be converted such that the columns will have
ANSI_PADDING ON, or will the OFF setting be preserved? I would assume that
they will be converted, but again, this is not explicitly stated anywhere.
If this information is listed somewhere, please direct me to the reference.
Thanks in advance for your time.
JeradJerad,
1)
I suggest you do a feedback on that BOL page. They should document what the setting will be when it
is deprecated.
I can bet a large sum that it will be ON. The Sybase heritage had the OFF behavior, where ANSI SQL
has the ON behavior. So, in some version (possibly 6.0) we could use this setting to change the
behavior. Over time, the ANSI (ON) behavior has become more and more dominating (tools defaulting to
this etc). Considering that some features require ON behavior (indexed views etc), and ANSI SQL is
ON, this will be ON when deprecated. But of course, the text should tell us that, so I suggest you
BOL feedback.
2) I have a feeling that no-one know at this moment what happens to existing databases when the
setting is deprecated. This is probably one of the things that MS need to work out with the
customers during beta. So, this I can understand why they can't comment on at this moment. But I
suggest you mention this in your BOL feedback. You never know, they might already know what will
happen...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jerad Rose" <no@.spam.com> wrote in message news:uRheZ08aHHA.348@.TK2MSFTNGP02.phx.gbl...
>I have a few questions regarding the ANSI_PADDING option. I see, according to MSDN
>(http://msdn2.microsoft.com/en-us/library/ms187403.aspx), that this option is deprecated:
>> This feature will be removed in a future version of Microsoft SQL
>> Server. Avoid using this feature in new development work, and
>> plan to modify applications that currently use this feature.
> My questions are:
> 1) What will this setting be fixed to once it is no longer supported? According to MSDN, their
> recommendation is that we always have it set to ON, and it states the default value is also ON.
> So I would assume that it will be fixed to ON once it is no longer supported, but I don't see this
> explicitly stated anywhere.
> 2) What will happen to existing databases with columns defined with this option turned on? Will
> they be converted such that the columns will have ANSI_PADDING ON, or will the OFF setting be
> preserved? I would assume that they will be converted, but again, this is not explicitly stated
> anywhere.
> If this information is listed somewhere, please direct me to the reference.
> Thanks in advance for your time.
> Jerad
>|||Thanks for your response, Tibor. I will follow your advise, and submit
feedback via BOL.
Thanks again.
Jerad
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e$4zIM%23aHHA.2076@.TK2MSFTNGP04.phx.gbl...
> Jerad,
> 1)
> I suggest you do a feedback on that BOL page. They should document what
the setting will be when it
> is deprecated.
> I can bet a large sum that it will be ON. The Sybase heritage had the OFF
behavior, where ANSI SQL
> has the ON behavior. So, in some version (possibly 6.0) we could use this
setting to change the
> behavior. Over time, the ANSI (ON) behavior has become more and more
dominating (tools defaulting to
> this etc). Considering that some features require ON behavior (indexed
views etc), and ANSI SQL is
> ON, this will be ON when deprecated. But of course, the text should tell
us that, so I suggest you
> BOL feedback.
>
> 2) I have a feeling that no-one know at this moment what happens to
existing databases when the
> setting is deprecated. This is probably one of the things that MS need to
work out with the
> customers during beta. So, this I can understand why they can't comment on
at this moment. But I
> suggest you mention this in your BOL feedback. You never know, they might
already know what will
> happen...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Jerad Rose" <no@.spam.com> wrote in message
news:uRheZ08aHHA.348@.TK2MSFTNGP02.phx.gbl...
> >I have a few questions regarding the ANSI_PADDING option. I see,
according to MSDN
> >(http://msdn2.microsoft.com/en-us/library/ms187403.aspx), that this
option is deprecated:
> >
> >> This feature will be removed in a future version of Microsoft SQL
> >> Server. Avoid using this feature in new development work, and
> >> plan to modify applications that currently use this feature.
> >
> > My questions are:
> >
> > 1) What will this setting be fixed to once it is no longer supported?
According to MSDN, their
> > recommendation is that we always have it set to ON, and it states the
default value is also ON.
> > So I would assume that it will be fixed to ON once it is no longer
supported, but I don't see this
> > explicitly stated anywhere.
> >
> > 2) What will happen to existing databases with columns defined with this
option turned on? Will
> > they be converted such that the columns will have ANSI_PADDING ON, or
will the OFF setting be
> > preserved? I would assume that they will be converted, but again, this
is not explicitly stated
> > anywhere.
> >
> > If this information is listed somewhere, please direct me to the
reference.
> >
> > Thanks in advance for your time.
> >
> > Jerad
> >
>|||> I can bet a large sum that it will be ON.
Tibor, I hope someone took you up on your bet. In fact, the setting will
always be ON. The topic is unclear (Thanks, Jerad, for submitting your
feedback). What's actually being deprecated is the ability to set the option
to OFF.
> 2) I have a feeling that no-one know at this moment what happens to
> existing databases when the setting is deprecated.
Again, you're correct. The migration/upgrade story for this is likely not
firmly in place given that doesn't go into effect for another two releases.
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
Download the latest version of Books Online from
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:e$4zIM%23aHHA.2076@.TK2MSFTNGP04.phx.gbl...
> Jerad,
> 1)
> I suggest you do a feedback on that BOL page. They should document what
> the setting will be when it is deprecated.
> I can bet a large sum that it will be ON. The Sybase heritage had the OFF
> behavior, where ANSI SQL has the ON behavior. So, in some version
> (possibly 6.0) we could use this setting to change the behavior. Over
> time, the ANSI (ON) behavior has become more and more dominating (tools
> defaulting to this etc). Considering that some features require ON
> behavior (indexed views etc), and ANSI SQL is ON, this will be ON when
> deprecated. But of course, the text should tell us that, so I suggest you
> BOL feedback.
>
> 2) I have a feeling that no-one know at this moment what happens to
> existing databases when the setting is deprecated. This is probably one of
> the things that MS need to work out with the customers during beta. So,
> this I can understand why they can't comment on at this moment. But I
> suggest you mention this in your BOL feedback. You never know, they might
> already know what will happen...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Jerad Rose" <no@.spam.com> wrote in message
> news:uRheZ08aHHA.348@.TK2MSFTNGP02.phx.gbl...
>>I have a few questions regarding the ANSI_PADDING option. I see,
>>according to MSDN
>>(http://msdn2.microsoft.com/en-us/library/ms187403.aspx), that this option
>>is deprecated:
>> This feature will be removed in a future version of Microsoft SQL
>> Server. Avoid using this feature in new development work, and
>> plan to modify applications that currently use this feature.
>> My questions are:
>> 1) What will this setting be fixed to once it is no longer supported?
>> According to MSDN, their recommendation is that we always have it set to
>> ON, and it states the default value is also ON. So I would assume that it
>> will be fixed to ON once it is no longer supported, but I don't see this
>> explicitly stated anywhere.
>> 2) What will happen to existing databases with columns defined with this
>> option turned on? Will they be converted such that the columns will have
>> ANSI_PADDING ON, or will the OFF setting be preserved? I would assume
>> that they will be converted, but again, this is not explicitly stated
>> anywhere.
>> If this information is listed somewhere, please direct me to the
>> reference.
>> Thanks in advance for your time.
>> Jerad
>|||> Tibor, I hope someone took you up on your bet.
I'm afraid no-one did... :-)
Thanks for jumping in and clarify, Gail.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Gail Erickson [MS]" <gaile@.online.microsoft.com> wrote in message
news:OK7GGNBbHHA.3408@.TK2MSFTNGP03.phx.gbl...
>> I can bet a large sum that it will be ON.
> Tibor, I hope someone took you up on your bet. In fact, the setting will always be ON. The topic
> is unclear (Thanks, Jerad, for submitting your feedback). What's actually being deprecated is the
> ability to set the option to OFF.
>> 2) I have a feeling that no-one know at this moment what happens to existing databases when the
>> setting is deprecated.
> Again, you're correct. The migration/upgrade story for this is likely not firmly in place given
> that doesn't go into effect for another two releases.
> --
> Gail Erickson [MS]
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
> Download the latest version of Books Online from
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:e$4zIM%23aHHA.2076@.TK2MSFTNGP04.phx.gbl...
>> Jerad,
>> 1)
>> I suggest you do a feedback on that BOL page. They should document what the setting will be when
>> it is deprecated.
>> I can bet a large sum that it will be ON. The Sybase heritage had the OFF behavior, where ANSI
>> SQL has the ON behavior. So, in some version (possibly 6.0) we could use this setting to change
>> the behavior. Over time, the ANSI (ON) behavior has become more and more dominating (tools
>> defaulting to this etc). Considering that some features require ON behavior (indexed views etc),
>> and ANSI SQL is ON, this will be ON when deprecated. But of course, the text should tell us that,
>> so I suggest you BOL feedback.
>>
>> 2) I have a feeling that no-one know at this moment what happens to existing databases when the
>> setting is deprecated. This is probably one of the things that MS need to work out with the
>> customers during beta. So, this I can understand why they can't comment on at this moment. But I
>> suggest you mention this in your BOL feedback. You never know, they might already know what will
>> happen...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Jerad Rose" <no@.spam.com> wrote in message news:uRheZ08aHHA.348@.TK2MSFTNGP02.phx.gbl...
>>I have a few questions regarding the ANSI_PADDING option. I see, according to MSDN
>>(http://msdn2.microsoft.com/en-us/library/ms187403.aspx), that this option is deprecated:
>> This feature will be removed in a future version of Microsoft SQL
>> Server. Avoid using this feature in new development work, and
>> plan to modify applications that currently use this feature.
>> My questions are:
>> 1) What will this setting be fixed to once it is no longer supported? According to MSDN, their
>> recommendation is that we always have it set to ON, and it states the default value is also ON.
>> So I would assume that it will be fixed to ON once it is no longer supported, but I don't see
>> this explicitly stated anywhere.
>> 2) What will happen to existing databases with columns defined with this option turned on? Will
>> they be converted such that the columns will have ANSI_PADDING ON, or will the OFF setting be
>> preserved? I would assume that they will be converted, but again, this is not explicitly stated
>> anywhere.
>> If this information is listed somewhere, please direct me to the reference.
>> Thanks in advance for your time.
>> Jerad
>>
>

订阅：博文 (Atom)

2012年2月18日星期六

Any Help regarding SQL Reporting Services

2012年2月13日星期一

Any book on SQL

any article regarding differences between SQL2K and Yukon

2012年2月11日星期六

anti-virus on sql server box?

ANSI_PADDING Deprecated

ANSI_PADDING Deprecated

ANSI_PADDING Deprecated

Sql ANSI Padding

Blog Archive

About Me