New to SQL - Old SAS School

I'm trying to understand Datawarehousing in the MS SQL World.
I'm a SAS Developer and have read reams of information on MSDN about Microso
fts Approach and DTS. But if I want to run a completely automated system in
Batch, is DTS still the approach.
Can anyone suggest a really good course in the UK or Book that might help?
I can see that SQL is a great tool as I've been getting used to it by contro
lling it from SAS - now I just want to go that little bit further.
Do I need to develop my own environment in VB.NET ?
Please help I'm getting overloaded with MS's TLAs and now need someone to te
ll me exactly what is neededHey, have u looked at www.swldts.com
--
SQL Server MVP - Colombia
"Jason Duncan-King" wrote:

> I'm trying to understand Datawarehousing in the MS SQL World.
> I'm a SAS Developer and have read reams of information on MSDN about Micro
softs Approach and DTS. But if I want to run a completely automated system
in Batch, is DTS still the approach.
> Can anyone suggest a really good course in the UK or Book that might help?
> I can see that SQL is a great tool as I've been getting used to it by cont
rolling it from SAS - now I just want to go that little bit further.
> Do I need to develop my own environment in VB.NET ?
> Please help I'm getting overloaded with MS's TLAs and now need someone to tell me
exactly what is needed|||In article <679321A7-CC23-43C8-A6A0-3CC74A543653@.microsoft.com>,
Alejandro Leguizamo (MVP) wrote:
> Hey, have u looked at www.swldts.com
>
www.sqldts.com right?
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
www.konesans.com - for all your consultancy needssql

New to SQL - Old SAS School

I'm trying to understand Datawarehousing in the MS SQL World.
I'm a SAS Developer and have read reams of information on MSDN about Microsofts Approach and DTS. But if I want to run a completely automated system in Batch, is DTS still the approach.
Can anyone suggest a really good course in the UK or Book that might help?
I can see that SQL is a great tool as I've been getting used to it by controlling it from SAS - now I just want to go that little bit further.
Do I need to develop my own environment in VB.NET ?
Please help I'm getting overloaded with MS's TLAs and now need someone to tell me exactly what is needed
Hey, have u looked at www.swldts.com
SQL Server MVP - Colombia
"Jason Duncan-King" wrote:

> I'm trying to understand Datawarehousing in the MS SQL World.
> I'm a SAS Developer and have read reams of information on MSDN about Microsofts Approach and DTS. But if I want to run a completely automated system in Batch, is DTS still the approach.
> Can anyone suggest a really good course in the UK or Book that might help?
> I can see that SQL is a great tool as I've been getting used to it by controlling it from SAS - now I just want to go that little bit further.
> Do I need to develop my own environment in VB.NET ?
> Please help I'm getting overloaded with MS's TLAs and now need someone to tell me exactly what is needed
|||In article <679321A7-CC23-43C8-A6A0-3CC74A543653@.microsoft.com>,
Alejandro Leguizamo (MVP) wrote:
> Hey, have u looked at www.swldts.com
>
www.sqldts.com right?
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
www.konesans.com - for all your consultancy needs

New system is slower than the old? Urgent help req'd please =(

My customer just purchased a system to replace their old system that handles
SQL. The new system apparently is abt 3-4 seconds slower in executing queri
es.
Their new system consists of:
P4-2.80GHz with HT
4GB PC3200 ram in dual channel mode
Intel D875PBZL motherboard
Adaptec 8 channel SATA RAID controller in PCI slot 2 or 3
2 x Seagate 80GB SATA mirrored for Win2K Server and SQL 2000 developer editi
on
6 x Seagate 80GB SATA RAID10 with 4 x approx 55GB partitions
PCI video card
The Old system consisted of:
Intel P4 2.0ghz
2gb ddr ram
on board promise hardware raid running the OS drive in mirror on 2x7200rpm i
de
drives
pci promise hardware raid running DATA drive in 3 drive stripe on 3x7200rpm
ide drives
win 2k server sp4 + patches
ms sql 2k developer edition
What could be causing it to be slower?Henry,
It all depends on if the queries that are being executed are the same on the
new system as the old system, other questions that need to be asked are
1. Have they changed the quantity of data being queried
2. Have they changed the index's on the table being queried
3. Are they maintaining the databases correctly - please don't say that the
database was migrated to the new server but none of the house keeping/mainte
nance scripts.
If you still have access to the old Server try running the same queries agai
nst the database whilst running a trace on proifiler this hsould show you if
the queries are genuinly being run more slowly. If they are not then this m
ay be a network issue conce
rning the new server.
Ed|||Could it be possible that the way the RAID is setup it's slower? i mean the
config of the HDs?
Does there seem to possibly be any hardware issue causing the performance de
crease?
What about Win2K server running on an HT enabled processor? Will Win2003 Ser
ver Standard address or utilise the HT better?|||anyone?

New system is slower than the old? Urgent help req'd please =(

My customer just purchased a system to replace their old system that handles SQL. The new system apparently is abt 3-4 seconds slower in executing queries.
Their new system consists of:
P4-2.80GHz with HT
4GB PC3200 ram in dual channel mode
Intel D875PBZL motherboard
Adaptec 8 channel SATA RAID controller in PCI slot 2 or 3
2 x Seagate 80GB SATA mirrored for Win2K Server and SQL 2000 developer edition
6 x Seagate 80GB SATA RAID10 with 4 x approx 55GB partitions
PCI video card
The Old system consisted of:
Intel P4 2.0ghz
2gb ddr ram
on board promise hardware raid running the OS drive in mirror on 2x7200rpm ide
drives
pci promise hardware raid running DATA drive in 3 drive stripe on 3x7200rpm
ide drives
win 2k server sp4 + patches
ms sql 2k developer edition
What could be causing it to be slower?
Henry,
It all depends on if the queries that are being executed are the same on the new system as the old system, other questions that need to be asked are
1. Have they changed the quantity of data being queried
2. Have they changed the index's on the table being queried
3. Are they maintaining the databases correctly - please don't say that the database was migrated to the new server but none of the house keeping/maintenance scripts.
If you still have access to the old Server try running the same queries against the database whilst running a trace on proifiler this hsould show you if the queries are genuinly being run more slowly. If they are not then this may be a network issue conce
rning the new server.
Ed
|||Could it be possible that the way the RAID is setup it's slower? i mean the config of the HDs?
Does there seem to possibly be any hardware issue causing the performance decrease?
What about Win2K server running on an HT enabled processor? Will Win2003 Server Standard address or utilise the HT better?
|||anyone?

New system is slower than the old? Urgent help req'd please =(

My customer just purchased a system to replace their old system that handles SQL. The new system apparently is abt 3-4 seconds slower in executing queries.
Their new system consists of
P4-2.80GHz with H
4GB PC3200 ram in dual channel mod
Intel D875PBZL motherboar
Adaptec 8 channel SATA RAID controller in PCI slot 2 or
2 x Seagate 80GB SATA mirrored for Win2K Server and SQL 2000 developer editio
6 x Seagate 80GB SATA RAID10 with 4 x approx 55GB partition
PCI video car
The Old system consisted of
Intel P4 2.0gh
2gb ddr ra
on board promise hardware raid running the OS drive in mirror on 2x7200rpm ide
drive
pci promise hardware raid running DATA drive in 3 drive stripe on 3x7200rpm
ide drive
win 2k server sp4 + patche
ms sql 2k developer editio
What could be causing it to be slower?Henry
It all depends on if the queries that are being executed are the same on the new system as the old system, other questions that need to be asked ar
1. Have they changed the quantity of data being querie
2. Have they changed the index's on the table being querie
3. Are they maintaining the databases correctly - please don't say that the database was migrated to the new server but none of the house keeping/maintenance scripts
If you still have access to the old Server try running the same queries against the database whilst running a trace on proifiler this hsould show you if the queries are genuinly being run more slowly. If they are not then this may be a network issue concerning the new server
Ed|||Could it be possible that the way the RAID is setup it's slower? i mean the config of the HDs
Does there seem to possibly be any hardware issue causing the performance decrease
What about Win2K server running on an HT enabled processor? Will Win2003 Server Standard address or utilise the HT better?|||anyone?

New SQL server to replace old SQL server

Hi
We are getting ready to replace an old NT old SQL server with a New
Server, New Windows and SQL.
I would like to setup the new server with a new name for testing and
once we have it working rename it to the old server name. There are some
ODBC connections that use the name and I suspect a few other things
setup that way as well.
Does that cause an issue with SQL to rename a server?
Thanks
Will
Hi,
After testing you can rename the sql server with out any issues.
Use:-
SP_DROPserver <servernaem>
Go
SP_ADDSERVER <name>,LOCAL
After this just restart sql server service.
Thanks
Hari
SQL Server MVP
"Will Kubly" <wkubly@.wi.rr.com> wrote in message
news:uf%23cyMnjFHA.3704@.TK2MSFTNGP10.phx.gbl...
> Hi
> We are getting ready to replace an old NT old SQL server with a New
> Server, New Windows and SQL.
> I would like to setup the new server with a new name for testing and once
> we have it working rename it to the old server name. There are some ODBC
> connections that use the name and I suspect a few other things setup that
> way as well.
> Does that cause an issue with SQL to rename a server?
> Thanks
> Will

New SQL server to replace old SQL server

Hi
We are getting ready to replace an old NT old SQL server with a New
Server, New Windows and SQL.
I would like to setup the new server with a new name for testing and
once we have it working rename it to the old server name. There are some
ODBC connections that use the name and I suspect a few other things
setup that way as well.
Does that cause an issue with SQL to rename a server?
Thanks
WillHi,
After testing you can rename the sql server with out any issues.
Use:-
SP_DROPserver <servernaem>
Go
SP_ADDSERVER <name>,LOCAL
After this just restart sql server service.
Thanks
Hari
SQL Server MVP
"Will Kubly" <wkubly@.wi.rr.com> wrote in message
news:uf%23cyMnjFHA.3704@.TK2MSFTNGP10.phx.gbl...
> Hi
> We are getting ready to replace an old NT old SQL server with a New
> Server, New Windows and SQL.
> I would like to setup the new server with a new name for testing and once
> we have it working rename it to the old server name. There are some ODBC
> connections that use the name and I suspect a few other things setup that
> way as well.
> Does that cause an issue with SQL to rename a server?
> Thanks
> Willsql

New SQL server to replace old SQL server

Hi
We are getting ready to replace an old NT old SQL server with a New
Server, New Windows and SQL.
I would like to setup the new server with a new name for testing and
once we have it working rename it to the old server name. There are some
ODBC connections that use the name and I suspect a few other things
setup that way as well.
Does that cause an issue with SQL to rename a server?
Thanks
WillHi,
After testing you can rename the sql server with out any issues.
Use:-
SP_DROPserver <servernaem>
Go
SP_ADDSERVER <name>,LOCAL
After this just restart sql server service.
Thanks
Hari
SQL Server MVP
"Will Kubly" <wkubly@.wi.rr.com> wrote in message
news:uf%23cyMnjFHA.3704@.TK2MSFTNGP10.phx.gbl...
> Hi
> We are getting ready to replace an old NT old SQL server with a New
> Server, New Windows and SQL.
> I would like to setup the new server with a new name for testing and once
> we have it working rename it to the old server name. There are some ODBC
> connections that use the name and I suspect a few other things setup that
> way as well.
> Does that cause an issue with SQL to rename a server?
> Thanks
> Will

New SQL Server 2005 JDBC 1.0 & Visual J++

We have a legacy Java application that we maintain in Visual J++; we are
moving to SQL Server 2005 and would like to switch it from an old WebLogic
JDBC driver to the new Microsoft SQL Server 2005 JDBC Driver.
However, we're noticing strange behavior with regard to instantiating the
"com.microsoft.sqlserver.jdbc.SQLServerDriver" class (no class def found
errors even though the sqljdbc.jar file is specified on the correct path in
the Classpath environment variable, and using FileMon we can see the app
finding the file).
I assume this means that we're running under the old, and unsupported,
Microsoft Java VM. Is it possible this VM does not support the new JDBC
driver?
Steven Bras
Tessitura Network, Inc.
Hi Steven,
Thank you for posting.
Regarding on the SQL Server 2005 JDBC driver, it is built against the SUN
J2se sdk 1.4 while the Microsoft's VJ++ jvm has already stoped updating, so
it dosn't support new built java components. I suggest you tried testing
the JDBC driver through standard SUN J2SE SDK to see whether it works. For
VJ++ we may consider using the OLEDB COM interface to access the SQL Server.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
|||Thanks for your response; can you point me to samples of how to use ole db in
java?
Steven Bras
Tessitura Network, Inc.
"Steven Cheng[MSFT]" wrote:

> Hi Steven,
> Thank you for posting.
> Regarding on the SQL Server 2005 JDBC driver, it is built against the SUN
> J2se sdk 1.4 while the Microsoft's VJ++ jvm has already stoped updating, so
> it dosn't support new built java components. I suggest you tried testing
> the JDBC driver through standard SUN J2SE SDK to see whether it works. For
> VJ++ we may consider using the OLEDB COM interface to access the SQL Server.
> Regards,
> Steven Cheng
> Microsoft Online Community Support
>
> ==================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>
|||Thanks for your response Steven,
I'm not quite sure about a complete example on connecting database through
OLEDB provider in VJ++, I think it'll be better to post in some VJ++ or
data accessing specific newsgroup. Also, have you any plan on migrating the
program to pure .net framework so that we have more choice on data
accessing to SQL Server?
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

New SQL Server 2005 JDBC 1.0 & Visual J++

We have a legacy Java application that we maintain in Visual J++; we are
moving to SQL Server 2005 and would like to switch it from an old WebLogic
JDBC driver to the new Microsoft SQL Server 2005 JDBC Driver.
However, we're noticing strange behavior with regard to instantiating the
"com.microsoft.sqlserver.jdbc.SQLServerDriver" class (no class def found
errors even though the sqljdbc.jar file is specified on the correct path in
the Classpath environment variable, and using FileMon we can see the app
finding the file).
I assume this means that we're running under the old, and unsupported,
Microsoft Java VM. Is it possible this VM does not support the new JDBC
driver?
Steven Bras
Tessitura Network, Inc.Hi Steven,
Thank you for posting.
Regarding on the SQL Server 2005 JDBC driver, it is built against the SUN
J2se sdk 1.4 while the Microsoft's VJ++ jvm has already stoped updating, so
it dosn't support new built Java components. I suggest you tried testing
the JDBC driver through standard SUN J2SE SDK to see whether it works. For
VJ++ we may consider using the OLEDB COM interface to access the SQL Server.
Regards,
Steven Cheng
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||Thanks for your response; can you point me to samples of how to use ole db i
n
java?
--
Steven Bras
Tessitura Network, Inc.
"Steven Cheng[MSFT]" wrote:

> Hi Steven,
> Thank you for posting.
> Regarding on the SQL Server 2005 JDBC driver, it is built against the SUN
> J2se sdk 1.4 while the Microsoft's VJ++ jvm has already stoped updating, s
o
> it dosn't support new built Java components. I suggest you tried testing
> the JDBC driver through standard SUN J2SE SDK to see whether it works. For
> VJ++ we may consider using the OLEDB COM interface to access the SQL Serve
r.
> Regards,
> Steven Cheng
> Microsoft Online Community Support
>
> ========================================
==========
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
==========
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>
>|||Thanks for your response Steven,
I'm not quite sure about a complete example on connecting database through
OLEDB provider in VJ++, I think it'll be better to post in some VJ++ or
data accessing specific newsgroup. Also, have you any plan on migrating the
program to pure .net framework so that we have more choice on data
accessing to SQL Server?
Regards,
Steven Cheng
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

New Server, How to transfer data from old server?

I'm using SQLServer 2000 on Windows 2000 Server.
We have just purchased a new server. The new server will
have the EXACT same file structure, computer name, and
static IP address as the old server. (We DO NOT use
replication).
I want transfer my databases, DTSs, and Logins to the new
server from the old.
How do I so this?
Do I only need to transfer the User databases or must I
also transfer the Master, Model, Tempdb, and msdb system
databases?
Thanksmaster contains the logins which will be needed on the new server...
You could backup/restore master, and msdb...
You could could the copy database wizard to copy the rest...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Brent Murphy" <brent.murphy@.us.schneider-electric.com> wrote in message
news:031d01c3af99$64620b70$a101280a@.phx.gbl...
> I'm using SQLServer 2000 on Windows 2000 Server.
> We have just purchased a new server. The new server will
> have the EXACT same file structure, computer name, and
> static IP address as the old server. (We DO NOT use
> replication).
> I want transfer my databases, DTSs, and Logins to the new
> server from the old.
> How do I so this?
> Do I only need to transfer the User databases or must I
> also transfer the Master, Model, Tempdb, and msdb system
> databases?
> Thanks
>|||Thanks Wayne.
So my Backed up Master DB will just overwrite whatever
Master DB is on the new server from the SQL Server 2000
install?
>--Original Message--
>master contains the logins which will be needed on the
new server...
>You could backup/restore master, and msdb...
>You could could the copy database wizard to copy the
rest...
>
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Computer Education Services Corporation (CESC),
Charlotte, NC
>www.computeredservices.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"Brent Murphy" <brent.murphy@.us.schneider-electric.com>
wrote in message
>news:031d01c3af99$64620b70$a101280a@.phx.gbl...
>> I'm using SQLServer 2000 on Windows 2000 Server.
>> We have just purchased a new server. The new server
will
>> have the EXACT same file structure, computer name, and
>> static IP address as the old server. (We DO NOT use
>> replication).
>> I want transfer my databases, DTSs, and Logins to the
new
>> server from the old.
>> How do I so this?
>> Do I only need to transfer the User databases or must I
>> also transfer the Master, Model, Tempdb, and msdb system
>> databases?
>> Thanks
>
>.
>|||Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Servers
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Brent Murphy" <brent.murphy@.us.schneider-electric.com> wrote in message
news:031d01c3af99$64620b70$a101280a@.phx.gbl...
> I'm using SQLServer 2000 on Windows 2000 Server.
> We have just purchased a new server. The new server will
> have the EXACT same file structure, computer name, and
> static IP address as the old server. (We DO NOT use
> replication).
> I want transfer my databases, DTSs, and Logins to the new
> server from the old.
> How do I so this?
> Do I only need to transfer the User databases or must I
> also transfer the Master, Model, Tempdb, and msdb system
> databases?
> Thanks
>|||One approach that we have used:
Stop sql services (disable) on old SQL server, rename that
server and re-ip it to something temporary.
Name new server and IP it to it's production name/ip.
Install SQL 2000 on it maintaining the exact file
structure of the original.
Apply whatever SP's / hotfixes to get SQL / W2k versions
to match across old box / new box.
Stop all SQL services on new box. Rename the folders
where your mdf's and ldf's are stored.
Copy the folders with the mdf's and ldf's from the
original server to the new server.
Start the services and go into enterprise mgr. and make
sure that all of the DB's are online.
This process will transfer all db's, logins, etc. We have
used it many times. The key is to have the file structure
match exactly as you mentioned. (and sp's)
You will have to recreate any scheduled tasks / maint
plans using this approach. Or you can probably copy them
also by moving the whole mssql folders instead of just
those that contain the data/log files. We haven't tried
this, but it should work.
HTH, Chuck
>--Original Message--
>I'm using SQLServer 2000 on Windows 2000 Server.
>We have just purchased a new server. The new server will
>have the EXACT same file structure, computer name, and
>static IP address as the old server. (We DO NOT use
>replication).
>I want transfer my databases, DTSs, and Logins to the new
>server from the old.
>How do I so this?
>Do I only need to transfer the User databases or must I
>also transfer the Master, Model, Tempdb, and msdb system
>databases?
>Thanks
>.
>|||Thanks Chuck for the informative answer!
I have a question. You said "Stop all SQL services on new
box. Rename the folders where your mdf's and ldf's are
stored."
If I have the same file/folder structure on the new
server, why do I need to rename the folders? I didn't
under stand that part. Is it just so you don't copy over
whatever was put in the orignal folders from the install?
>--Original Message--
>One approach that we have used:
>Stop sql services (disable) on old SQL server, rename
that
>server and re-ip it to something temporary.
>Name new server and IP it to it's production name/ip.
>Install SQL 2000 on it maintaining the exact file
>structure of the original.
>Apply whatever SP's / hotfixes to get SQL / W2k versions
>to match across old box / new box.
>Stop all SQL services on new box. Rename the folders
>where your mdf's and ldf's are stored.
>Copy the folders with the mdf's and ldf's from the
>original server to the new server.
>Start the services and go into enterprise mgr. and make
>sure that all of the DB's are online.
>This process will transfer all db's, logins, etc. We
have
>used it many times. The key is to have the file
structure
>match exactly as you mentioned. (and sp's)
>You will have to recreate any scheduled tasks / maint
>plans using this approach. Or you can probably copy them
>also by moving the whole mssql folders instead of just
>those that contain the data/log files. We haven't tried
>this, but it should work.
>HTH, Chuck
>>--Original Message--
>>I'm using SQLServer 2000 on Windows 2000 Server.
>>We have just purchased a new server. The new server
will
>>have the EXACT same file structure, computer name, and
>>static IP address as the old server. (We DO NOT use
>>replication).
>>I want transfer my databases, DTSs, and Logins to the
new
>>server from the old.
>>How do I so this?
>>Do I only need to transfer the User databases or must I
>>also transfer the Master, Model, Tempdb, and msdb system
>>databases?
>>Thanks
>>.
>.
>|||Sorry took so long for me to get back.. You've probably already
figured this out, but the goal was to rename the data folders on the
new install in case anything went sideways when you copied the data
folders from the original install, so you can go back. Good luck!
Chuck
"Brent Murphy" <brent.murphy@.us.schneier-electric.com> wrote in message news:<0bc201c3b035$e1c4eb40$a101280a@.phx.gbl>...
> Thanks Chuck for the informative answer!
> I have a question. You said "Stop all SQL services on new
> box. Rename the folders where your mdf's and ldf's are
> stored."
> If I have the same file/folder structure on the new
> server, why do I need to rename the folders? I didn't
> under stand that part. Is it just so you don't copy over
> whatever was put in the orignal folders from the install?
>

New Pull Subscription - Trans Repli - Use old snapshot...

How do I created a new Pull subscription from a transaction replication
publisher without having to run the Sanpshot again?
When I create a new Pull Subscription, it says "Snapshot not ready". After I
run Sanpshot, then it starts.
Running the snapshot forces me to take the production server down for 2
hours, and can not always do this.
Thanks and God Bless,
ThomBeaux
use the concurrent snapshot option. God bless u2.
Hilary Cotter
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
"ThomBeaux" <ThomBeaux@.NoSpam.Com> wrote in message
news:60B3F87F-ED59-4030-B30B-E61B145754C5@.microsoft.com...
> How do I created a new Pull subscription from a transaction replication
> publisher without having to run the Sanpshot again?
> When I create a new Pull Subscription, it says "Snapshot not ready". After
> I
> run Sanpshot, then it starts.
> Running the snapshot forces me to take the production server down for 2
> hours, and can not always do this.
> --
> Thanks and God Bless,
> ThomBeaux
|||What part on the Wizard asks for for the concurrent snapshot optin
Thanks and God Bless,
ThomBeaux
"Hilary Cotter" wrote:

> use the concurrent snapshot option. God bless u2.
> --
> Hilary Cotter
> 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
>
> "ThomBeaux" <ThomBeaux@.NoSpam.Com> wrote in message
> news:60B3F87F-ED59-4030-B30B-E61B145754C5@.microsoft.com...
>
>
|||As well as Hilary's advice, if you are using SQL Server 2005 there is the
option to "initialize with backup". In the CTP SP2 there is also the option
of 'database snapshot' for the sync type AFAIR.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||after creating your publication right click on it and go to the snapshot
tab, you should find it there. Its something about minimize locking during
snapshot generation.
Hilary Cotter
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
"ThomBeaux" <ThomBeaux@.NoSpam.Com> wrote in message
news:EDD53985-2C00-4151-8902-C08AAC5CEE52@.microsoft.com...[vbcol=seagreen]
> What part on the Wizard asks for for the concurrent snapshot optin
> --
> Thanks and God Bless,
> ThomBeaux
>
> "Hilary Cotter" wrote:

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.