Duble \\ in physical file name

I recently reviewd our Veritas backup jobs and found several databases
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thing
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. LaoyanGenerally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan

Duble \\ in physical file name

I recently reviewd our Veritas backup jobs and found several databases
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thing
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. Laoyan
Generally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan

Duble \\ in physical file name

I recently reviewd our Veritas backup jobs and found several databases
failing on backup. I then went through the native SQL Backup processes and
found that these databases were indeed backing up to disk, but not thru the
Veritas client. After further review all of these database all had one thin
g
in common. They all had E:\PathName\\FileName.MDF in their filenames.
(Notice the double \\) I corrected this by detaching and reattaching with
move. What I wanna know is if anyone noticed this problem and what is
creating it?
Thanx for your help,
Raoul B. LaoyanGenerally it's Enterprise Manager. If the Default Data or Default Log
directory as viewed in Server Properties in EM have a trailing backslash
then new databases created without specifying filenames will have a \\ in
their path. To resolve this simply remove the trailing backslash from the
default data and log paths.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Raoul Laoyan" <RaoulLaoyan@.discussions.microsoft.com> wrote in message
news:A049D4BF-0FBA-49BA-B031-CF6B21021B2A@.microsoft.com...
>I recently reviewd our Veritas backup jobs and found several databases
> failing on backup. I then went through the native SQL Backup processes
> and
> found that these databases were indeed backing up to disk, but not thru
> the
> Veritas client. After further review all of these database all had one
> thing
> in common. They all had E:\PathName\\FileName.MDF in their filenames.
> (Notice the double \\) I corrected this by detaching and reattaching with
> move. What I wanna know is if anyone noticed this problem and what is
> creating it?
> Thanx for your help,
> Raoul B. Laoyan

Dual Quad Core vs 4 Dual Core Performance

We like the idea of Dual Quad Cores 'cos now you can license SQL for 2
physical sockets as opposed to 4 if we were going with 4 dual core chips. Am
I right there from a licnensing perspective ?
Also what other differences should I be aware of especially from a
performance standpoint ? I would think they should both be similar..
ThanksRegarding to the licensing, you pay for license for each physical CPU
socket. You don't need separate licenses for each core.
--
Ekrem Önsoy
"Hassan" <hassan@.test.com> wrote in message
news:uIGZQDrRIHA.3676@.TK2MSFTNGP06.phx.gbl...
> We like the idea of Dual Quad Cores 'cos now you can license SQL for 2
> physical sockets as opposed to 4 if we were going with 4 dual core chips.
> Am I right there from a licnensing perspective ?
> Also what other differences should I be aware of especially from a
> performance standpoint ? I would think they should both be similar..
> Thanks
>
>|||Dear Hassan,
Your reasoning appears to be correct. You want to cram as many cores/cpu
power per socket if you are going with a per processor based licensing
scheme. A quad core or better CPU is what you would want to fully exploit
SQL Server licensing!
Regards,
James Simpson
Straightway Technologies Inc.|||At the high-end of the performance spectrum you should get better
performance (especially for large-data-volume queries) with a quad dual core
arrangement. This does assume that you have sufficiently capable I/O
subsystem bolted up to the server.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Hassan" <hassan@.test.com> wrote in message
news:uIGZQDrRIHA.3676@.TK2MSFTNGP06.phx.gbl...
> We like the idea of Dual Quad Cores 'cos now you can license SQL for 2
> physical sockets as opposed to 4 if we were going with 4 dual core chips.
> Am I right there from a licnensing perspective ?
> Also what other differences should I be aware of especially from a
> performance standpoint ? I would think they should both be similar..
> Thanks
>
>|||If you are saying that four dual-core sockets would give you better
performance than two quad-core sockets, I doubt it. I understand your
reasoning. But the technology progres is such that you generally get better
overall system configurations with newer processors. In other words, you may
find quad-core-socket servers come with better chipsets and PCI-E slots, and
so on.
Linchi
"TheSQLGuru" wrote:
> At the high-end of the performance spectrum you should get better
> performance (especially for large-data-volume queries) with a quad dual core
> arrangement. This does assume that you have sufficiently capable I/O
> subsystem bolted up to the server.
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
> "Hassan" <hassan@.test.com> wrote in message
> news:uIGZQDrRIHA.3676@.TK2MSFTNGP06.phx.gbl...
> > We like the idea of Dual Quad Cores 'cos now you can license SQL for 2
> > physical sockets as opposed to 4 if we were going with 4 dual core chips.
> > Am I right there from a licnensing perspective ?
> >
> > Also what other differences should I be aware of especially from a
> > performance standpoint ? I would think they should both be similar..
> >
> > Thanks
> >
> >
> >
>
>

Dual core or hyperthreading enabled

How can I find out if its a dual core box or a box with hyperthreading
enabled ?
So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
am using SQL 2005. Even if not through SQL, what are the other ways that I
can do so by running a command ?
Thanks
It's most likely dual core. Check the CPU model number. If it's the Opteron
8000 series, it's dual core.
Linchi
"Hassan" wrote:

> How can I find out if its a dual core box or a box with hyperthreading
> enabled ?
> So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
> CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
> that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
> am using SQL 2005. Even if not through SQL, what are the other ways that I
> can do so by running a command ?
> Thanks
>
>

Dual core or hyperthreading enabled

How can I find out if its a dual core box or a box with hyperthreading
enabled ?
So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
am using SQL 2005. Even if not through SQL, what are the other ways that I
can do so by running a command ?
ThanksIt's most likely dual core. Check the CPU model number. If it's the Opteron
8000 series, it's dual core.
Linchi
"Hassan" wrote:

> How can I find out if its a dual core box or a box with hyperthreading
> enabled ?
> So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
> CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
> that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
> am using SQL 2005. Even if not through SQL, what are the other ways that I
> can do so by running a command ?
> Thanks
>
>

Dual core or hyperthreading enabled

How can I find out if its a dual core box or a box with hyperthreading
enabled ?
So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
am using SQL 2005. Even if not through SQL, what are the other ways that I
can do so by running a command ?
ThanksIt's most likely dual core. Check the CPU model number. If it's the Opteron
8000 series, it's dual core.
Linchi
"Hassan" wrote:
> How can I find out if its a dual core box or a box with hyperthreading
> enabled ?
> So I know its a 4 physical processor box as its a DL 585 G2. But I see 8
> CPUs in Task manager. Now is it hyperthreading enabled or is it dual core
> that shows it as 8 procs ? Is there an easy way to find that using SQL ? I
> am using SQL 2005. Even if not through SQL, what are the other ways that I
> can do so by running a command ?
> Thanks
>
>