Unbundling SQLCMD From SQL Server 2005 ?

Hi all,

I was wondering if it would make sense for Microsoft to unbundle SQLCMD from SQL Server 2005. The tool is a basically a command line *client* tool, right?

I have a machine that I would love to put SQLCMD on to do remote admin work but to do so I need to install SQL Server 2005 Express, at a minimum. I would love to be able to just download SQLCMD (and of course the needed DLLs) and install it.

What do you think?

Thanks.

-Alan

This question was answered in a posting to 'microsoft.public.sqlserver.tools' by Jasper Smith:

You can get it from here
http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en#filelist

You will need the SQL Native client and SQLCMD downloads. The filenames are

sqlncli.msi
SQLServer2005_SQLCMD.msi

HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com

Unbundling SQLCMD From SQL Server 2005 ?

Hi all,
I was wondering if it would make sense for Microsoft to unbundle SQLCMD
from SQL Server 2005. The tool is a basically a command line *client*,
right?
I have a machine that I would love to put SQLCMD on to do remote admin
work but to do so I need to install SQL Server 2005 Express, at a
minimum. I would love to be able to just download SQLCMD (and of course
the needed DLLs) and install it.
What do you think?
-Alan
You can get it from here
http://www.microsoft.com/downloads/d...ng=en#filelist
You will need the SQL Native client and SQLCMD downloads. The filenames are
sqlncli.msi
SQLServer2005_SQLCMD.msi
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Alan Foxmore" <AFoxmore@.yahoo.com> wrote in message
news:OH2T3m%23VGHA.5076@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I was wondering if it would make sense for Microsoft to unbundle SQLCMD
> from SQL Server 2005. The tool is a basically a command line *client*,
> right?
> I have a machine that I would love to put SQLCMD on to do remote admin
> work but to do so I need to install SQL Server 2005 Express, at a minimum.
> I would love to be able to just download SQLCMD (and of course the needed
> DLLs) and install it.
> What do you think?
> -Alan
>
|||"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:usOldSCWGHA.3332@.TK2MSFTNGP02.phx.gbl...
> You can get it from here
> http://www.microsoft.com/downloads/d...ng=en#filelist
> You will need the SQL Native client and SQLCMD downloads. The
> filenames are
> sqlncli.msi
> SQLServer2005_SQLCMD.msi
> --
> HTH,
> Jasper Smith (SQL Server MVP)
> http://www.sqldbatips.com
Wonderful! Thanks so much!!!!!

> "Alan Foxmore" <AFoxmore@.yahoo.com> wrote in message
> news:OH2T3m%23VGHA.5076@.TK2MSFTNGP11.phx.gbl...
>

Regarding Openrowset

In the following line of code, does anyone know what the letter N represents
that appears right after the word Bulk
FROM OPENROWSET(BULK N'C:\Text1.txt', SINGLE_BLOB) AS Document"Alvin Clark" <alvin.clark@.accudata.com> wrote in message
news:e6kl7vYEIHA.4228@.TK2MSFTNGP02.phx.gbl...
> In the following line of code, does anyone know what the letter N
> represents that appears right after the word Bulk
> FROM OPENROWSET(BULK N'C:\Text1.txt', SINGLE_BLOB) AS Document
The letter "N" preceding a string constant indicates that the string is a
unicode string. For additional information, refer to BOL (index - unicode
constants)|||This one throws me a little too. However, it has to do with all the
different character sets that SQL Server supports (coalitions).
The string:
'normal string'
uses a character set English speakers would consider normal. However, we
ain't the only ones on the planet. So SQL Server also supports UNICODE (with
the variable types of nchar, nvarchar, & ntext).
The string:
N'København'
is a Unicode/nchar string (copied from 2000 BOL - NCHAR page)
Therefore, the N'string' syntax is a way of being safe with your literal
strings and making sure some change in the character set doesn't mess you up
somewhere.
Jay
(Man I hope I got this right. About to find out...)
"Alvin Clark" <alvin.clark@.accudata.com> wrote in message
news:e6kl7vYEIHA.4228@.TK2MSFTNGP02.phx.gbl...
> In the following line of code, does anyone know what the letter N
> represents that appears right after the word Bulk
> FROM OPENROWSET(BULK N'C:\Text1.txt', SINGLE_BLOB) AS Document
>

is NOT a parameter

When I use this line of code:

CASE WHEN d.StatusId IN ('XF','?','XT') THEN 1 ELSE 0 END AS Status

MS Reporting Services 2005 thinks that ? is a parameter. I know that I can use a stored proc to prevent this, but I would rather not.

Does anyone have suggestions on how to prevent this from occuring?

How about (not testing but it should work):

Code Snippet

CASE WHEN d.StatusID IN ('XF',CHAR(63),'XT') THEN 1 ELSE 0 END AS Status

>L<|||

Thanks Lisa,

That works. I also found that you can remove the <Parameter> tag from the code to fix it.

floyd

|||Nice username. HAHAHA sql