database file locations: win

Showing posts with label win. Show all posts

Wednesday, March 21, 2012

new server to install, Win 2003 x64 will be used... which SQL Version?

Hi,
I have to install a new server and I am a little confused about working
combinations between 30bits, x64 and IA64...
My server use intel Xeon processors with EMT64.
So I want to install Windows 2003 x64 Ent.
but which version of SQL Server can I install?
the 64bits?
32bits + SP4 (Sql2k64sp4.exe)?
Also I have to install Reporting Services, Analysis Services & Sharepoint.
Does everything works on Win x64?
I'm using SQL Server 2000 enterprise edition.
thanks for your answer.
Jerome.You need the SQL Server 2000 (64-bit) edition.
http://www.microsoft.com/sql/64bit/default.mspx
--
--Brian
(Please reply to the newsgroups only.)
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:e%2313sduuFHA.3764@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have to install a new server and I am a little confused about working
> combinations between 30bits, x64 and IA64...
> My server use intel Xeon processors with EMT64.
> So I want to install Windows 2003 x64 Ent.
> but which version of SQL Server can I install?
> the 64bits?
> 32bits + SP4 (Sql2k64sp4.exe)?
> Also I have to install Reporting Services, Analysis Services & Sharepoint.
> Does everything works on Win x64?
> I'm using SQL Server 2000 enterprise edition.
> thanks for your answer.
> Jerome.
>|||what you really need; you need to wait for sql 2005 and it'll be a LOT
better|||unfortunatly its an hardware migration process.
we change an old server to a new one
so we can't deploy 2005.
but I have to insure that the 64bits edition (of SQL, RS, AS) works
correctly on Win 2003 x64.
if there is any issue or compatibility problem, I'll use the 32bit edition.
<dbahooker@.hotmail.com> wrote in message
news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
> what you really need; you need to wait for sql 2005 and it'll be a LOT
> better
>|||Hi
No, 32 Bit plus SP4.
SQL Server 2000 64 Bit is complied for the Intel Itanium Processor and will
not run on Xeons.
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/
"Brian Lawton" <brian.k.lawton@.redtailcreek.com> wrote in message
news:%23QD6nsuuFHA.1472@.TK2MSFTNGP15.phx.gbl...
> You need the SQL Server 2000 (64-bit) edition.
> http://www.microsoft.com/sql/64bit/default.mspx
> --
> --Brian
> (Please reply to the newsgroups only.)
>
> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
> news:e%2313sduuFHA.3764@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have to install a new server and I am a little confused about working
>> combinations between 30bits, x64 and IA64...
>> My server use intel Xeon processors with EMT64.
>> So I want to install Windows 2003 x64 Ent.
>> but which version of SQL Server can I install?
>> the 64bits?
>> 32bits + SP4 (Sql2k64sp4.exe)?
>> Also I have to install Reporting Services, Analysis Services &
>> Sharepoint.
>> Does everything works on Win x64?
>> I'm using SQL Server 2000 enterprise edition.
>> thanks for your answer.
>> Jerome.
>>
>|||If you are going to install the 64-bit version of the Win2K3 make sure:
1) you install SP1 of Win2K3 x64 -- and
2) you use SP4
Both are required to run AS2K on x64 hardware with a 64-bit OS.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:ONOy27vuFHA.2072@.TK2MSFTNGP14.phx.gbl...
> unfortunatly its an hardware migration process.
> we change an old server to a new one
> so we can't deploy 2005.
> but I have to insure that the 64bits edition (of SQL, RS, AS) works
> correctly on Win 2003 x64.
> if there is any issue or compatibility problem, I'll use the 32bit
> edition.
>
> <dbahooker@.hotmail.com> wrote in message
> news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
>> what you really need; you need to wait for sql 2005 and it'll be a LOT
>> better
>|||Thankls.
I have all of this on my CD Roms...
so finally, there is no issue in mind(?)
"Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message
news:%23ultf2XvFHA.4032@.TK2MSFTNGP15.phx.gbl...
> If you are going to install the 64-bit version of the Win2K3 make sure:
> 1) you install SP1 of Win2K3 x64 -- and
> 2) you use SP4
> Both are required to run AS2K on x64 hardware with a 64-bit OS.
> --
> Dave Wickert [MSFT]
> dwickert@.online.microsoft.com
> Program Manager
> BI Systems Team
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
> news:ONOy27vuFHA.2072@.TK2MSFTNGP14.phx.gbl...
>> unfortunatly its an hardware migration process.
>> we change an old server to a new one
>> so we can't deploy 2005.
>> but I have to insure that the 64bits edition (of SQL, RS, AS) works
>> correctly on Win 2003 x64.
>> if there is any issue or compatibility problem, I'll use the 32bit
>> edition.
>>
>> <dbahooker@.hotmail.com> wrote in message
>> news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
>> what you really need; you need to wait for sql 2005 and it'll be a LOT
>> better
>>
>|||I will be deploying this same setup... Windows 2003 Standard x64
Edition running SQL Server 2000 Enterprise Edition SP4. The server I'm
running on has 8GB of RAM. Does anyone know how much RAM SQL Server
will use? My understanding is that this is not an AWE situtation
because the OS can natively address all 8GB of RAM.
Any advice on maximizing this setup would be greatly appreciated.
Thanks.
--
george sarlas
gsarlas@.yahoo.com|||> My understanding is that this is not an AWE situtation
> because the OS can natively address all 8GB of RAM.
You are right, SQL Server can access up to 512Gb of RAM, which is the
maximum currently supported by Win2K3 Server.
--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell|||I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
AWE in SQL Server. But to support more than 4GB of RAM, I needed to
install SQL 2000 SP4 and the SP4 AWE Hotfix
(http://support.microsoft.com/default.aspx?kbid=899761).
-george|||If you have 64bit SQL 2k you do not need to enable AWE. The knowledge
base article you quote only applies to 32bit SQL 2k. 64bit SQL 2k can
address the maximum amount of memory that Win2k3 can support (which is
512Gb) without turning on any special settings.
--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell
In article <1130256929.245741.68610@.g44g2000cwa.googlegroups.com>,
gsarlas@.yahoo.com says...
> I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
> AWE in SQL Server. But to support more than 4GB of RAM, I needed to
> install SQL 2000 SP4 and the SP4 AWE Hotfix
> (http://support.microsoft.com/default.aspx?kbid=899761).
> -george
>|||Just for clarification...
Unfortunately, SQL Server 2000 64-bit Edition does not work with x64
processors. It only works with the Itanium processor. I am running
32-bit SQL Server 2000 on 64-bit Windows 2003, thus I had to enable
AWE.
-george
Darren Gosbell wrote:
> If you have 64bit SQL 2k you do not need to enable AWE. The knowledge
> base article you quote only applies to 32bit SQL 2k. 64bit SQL 2k can
> address the maximum amount of memory that Win2k3 can support (which is
> 512Gb) without turning on any special settings.
> --
> Regards
> Darren Gosbell [MCSD]
> <dgosbell_at_yahoo_dot_com>
> Blog: http://www.geekswithblogs.net/darrengosbell
> In article <1130256929.245741.68610@.g44g2000cwa.googlegroups.com>,
> gsarlas@.yahoo.com says...
> > I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
> > AWE in SQL Server. But to support more than 4GB of RAM, I needed to
> > install SQL 2000 SP4 and the SP4 AWE Hotfix
> > (http://support.microsoft.com/default.aspx?kbid=899761).
> >
> > -george
> >
> >

new server to install, Win 2003 x64 will be used... which SQL Version?

Monday, March 12, 2012

New Production Server - Orphaned Users

Hi,
I have to move 5 databases from an old production server to a new production
server.
Old Production Server: Win 2K Server, SQL 2000 SP2
New Production Server:Win 2K3 Server, SQL 2000 SP4
I am creating the new server from scratch. Since I can't run SQL Server SP2
on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
I backed up system databases on Old Production server and restored them on
Staging and applied SP4 to the Staging server. Then I backed up system
databases on Staging and restored them on New Production Server since both o
f
them are now at the same Service Pack Level. I have to do it this way to
avoid applying SP4 directly to the old Production server.
Then I detached and attached the User databases on the New Production server
from Old Production server. My question is - would I still have orphaned
users? Thanks in advance.If I followed your chain correctly, you basically took your system databases
from a to b to c. Then
you take your user databases from a to c. This should mean that the logins e
xists with correct SID -
i.e., no orphaned users.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new producti
on
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server SP
2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production serv
er
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.|||Hi
http://dimantdatabasesolutions.blog...on.
html
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new
> production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server
> SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
> of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production
> server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.

New Production Server - Orphaned Users

Hi,
I have to move 5 databases from an old production server to a new production
server.
Old Production Server: Win 2K Server, SQL 2000 SP2
New Production Server:Win 2K3 Server, SQL 2000 SP4
I am creating the new server from scratch. Since I can't run SQL Server SP2
on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
I backed up system databases on Old Production server and restored them on
Staging and applied SP4 to the Staging server. Then I backed up system
databases on Staging and restored them on New Production Server since both of
them are now at the same Service Pack Level. I have to do it this way to
avoid applying SP4 directly to the old Production server.
Then I detached and attached the User databases on the New Production server
from Old Production server. My question is - would I still have orphaned
users? Thanks in advance.
If I followed your chain correctly, you basically took your system databases from a to b to c. Then
you take your user databases from a to c. This should mean that the logins exists with correct SID -
i.e., no orphaned users.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.
|||Hi
http://dimantdatabasesolutions.blogspot.com/2007/04/sql-or-windows-authentication.html
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new
> production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server
> SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
> of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production
> server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.

New Production Server - Orphaned Users

Hi,
I have to move 5 databases from an old production server to a new production
server.
Old Production Server: Win 2K Server, SQL 2000 SP2
New Production Server:Win 2K3 Server, SQL 2000 SP4
I am creating the new server from scratch. Since I can't run SQL Server SP2
on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
I backed up system databases on Old Production server and restored them on
Staging and applied SP4 to the Staging server. Then I backed up system
databases on Staging and restored them on New Production Server since both of
them are now at the same Service Pack Level. I have to do it this way to
avoid applying SP4 directly to the old Production server.
Then I detached and attached the User databases on the New Production server
from Old Production server. My question is - would I still have orphaned
users? Thanks in advance.If I followed your chain correctly, you basically took your system databases from a to b to c. Then
you take your user databases from a to c. This should mean that the logins exists with correct SID -
i.e., no orphaned users.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.|||Hi
http://dimantdatabasesolutions.blogspot.com/2007/04/sql-or-windows-authentication.html
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDCD1A18-7031-4BA4-A08D-4363E296CD77@.microsoft.com...
> Hi,
> I have to move 5 databases from an old production server to a new
> production
> server.
> Old Production Server: Win 2K Server, SQL 2000 SP2
> New Production Server:Win 2K3 Server, SQL 2000 SP4
> I am creating the new server from scratch. Since I can't run SQL Server
> SP2
> on Win 2K3 OS, I have a Staging Server running Win 2K and SQL 2000 SP2.
> I backed up system databases on Old Production server and restored them on
> Staging and applied SP4 to the Staging server. Then I backed up system
> databases on Staging and restored them on New Production Server since both
> of
> them are now at the same Service Pack Level. I have to do it this way to
> avoid applying SP4 directly to the old Production server.
> Then I detached and attached the User databases on the New Production
> server
> from Old Production server. My question is - would I still have orphaned
> users? Thanks in advance.

Monday, February 20, 2012

New Crystal Report Question

Hi guyz! i have a problem with my crystal report 9. im using vb6 in win xp. my prob is when i print my report in second attempt it will just eject the paper without print. but in first, its fine..

here's my code:

MyReportPrintCheck.DiscardSavedData
Set printer = Printers(cmbprinter.ListIndex)
MyReportPrintCheck.SelectPrinter printer.DriverName, printer.DeviceName, printer.Port
MyReportPrintCheck.PaperOrientation = crDefaultPaperOrientation
MyReportPrintCheck.PaperSize = crPaperLetter
MyReportPrintCheck.PrintOut False <-- i think the "False" here is the problem because when i remove the false it will print though it will take time coz it will prompt me a message if i will print all or selection..thats why i put "False" here so that when i click the Print button.. it will automatically print. can anyone help me?

Set MyReportPrintCheck = Nothing

i really appreciate ur reply...

atzMake sure the second page is not empty|||yes, my second report is already empty... but still it will never print... it still eject the paper... when i install my vb6 and cr9 in win 98 and try, it works fine! but when i transfer, i mean install it in win xp. there goes the problem... i think mybe there something with my code... can you give me an example? thanks for your reply... :)

Wednesday, March 21, 2012

new server to install, Win 2003 x64 will be used... which SQL Version?

new server to install, Win 2003 x64 will be used... which SQL Version?

new server to install, Win 2003 x64 will be used... which SQL Version?

new server to install, Win 2003 x64 will be used... which SQL Version?

Monday, March 12, 2012

New Production Server - Orphaned Users

New Production Server - Orphaned Users

New Production Server - Orphaned Users

Monday, February 20, 2012

New Crystal Report Question

database file locations

Blog Archive

About Me