Question about Log Shipping: Secondary non-writable?

Hi, i think i'm just getting confused with all the reading. I have 2
servers, A is live and B is doing nothing. I want to create some kind
of warm standby so I looked at replication and log shipping. Repl
seems to be kinda messy so i think i will go with log shipping.
Database is around 2gigs and i can live with an interval of around
1/hr log ship.
Now my question is i read somewhere it says the databse on the second
server is read only...non writable? So what happens if i need to
failover and make the secondary server live? Is it then only readable
but unwritable? What good is that? Any ideas?>...or i just got it
wrong?
The secondary is unwriteable as long as you are shipping logs. Once you
take it live, it becomes he 'real' database server and starts servicing
requests. Note that I am answering your questions on a conceptual level, if
you want the technical details of HOW that happens, that is for a follow-up
question.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"slycat" <slycat@.consultant.com> wrote in message
news:dec83278.0411091807.15bb247a@.posting.google.c om...
> Hi, i think i'm just getting confused with all the reading. I have 2
> servers, A is live and B is doing nothing. I want to create some kind
> of warm standby so I looked at replication and log shipping. Repl
> seems to be kinda messy so i think i will go with log shipping.
> Database is around 2gigs and i can live with an interval of around
> 1/hr log ship.
> Now my question is i read somewhere it says the databse on the second
> server is read only...non writable? So what happens if i need to
> failover and make the secondary server live? Is it then only readable
> but unwritable? What good is that? Any ideas?>...or i just got it
> wrong?
|||There is a great section in SQL Books on Line which describes in detail, how
to make a secondary database primary... including how to get the logins to
match... Search for Log shipping ...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"slycat" <slycat@.consultant.com> wrote in message
news:dec83278.0411091807.15bb247a@.posting.google.c om...
> Hi, i think i'm just getting confused with all the reading. I have 2
> servers, A is live and B is doing nothing. I want to create some kind
> of warm standby so I looked at replication and log shipping. Repl
> seems to be kinda messy so i think i will go with log shipping.
> Database is around 2gigs and i can live with an interval of around
> 1/hr log ship.
> Now my question is i read somewhere it says the databse on the second
> server is read only...non writable? So what happens if i need to
> failover and make the secondary server live? Is it then only readable
> but unwritable? What good is that? Any ideas?>...or i just got it
> wrong?
|||Log Shipping in SQL Server 2000, Part 1
http://www.winnetmag.com/Article/Art...056/23056.html
Log Shipping in SQL Server 2000, Part 2
http://www.winnetmag.com/Article/Art...230/23230.html
/Sukhdev

Question about Log Shipping: Secondary non-writable?

Hi, i think i'm just getting confused with all the reading. I have 2
servers, A is live and B is doing nothing. I want to create some kind
of warm standby so I looked at replication and log shipping. Repl
seems to be kinda messy so i think i will go with log shipping.
Database is around 2gigs and i can live with an interval of around
1/hr log ship.
Now my question is i read somewhere it says the databse on the second
server is read only...non writable? So what happens if i need to
failover and make the secondary server live? Is it then only readable
but unwritable? What good is that? Any ideas?>...or i just got it
wrong?The secondary is unwriteable as long as you are shipping logs. Once you
take it live, it becomes he 'real' database server and starts servicing
requests. Note that I am answering your questions on a conceptual level, if
you want the technical details of HOW that happens, that is for a follow-up
question.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"slycat" <slycat@.consultant.com> wrote in message
news:dec83278.0411091807.15bb247a@.posting.google.com...
> Hi, i think i'm just getting confused with all the reading. I have 2
> servers, A is live and B is doing nothing. I want to create some kind
> of warm standby so I looked at replication and log shipping. Repl
> seems to be kinda messy so i think i will go with log shipping.
> Database is around 2gigs and i can live with an interval of around
> 1/hr log ship.
> Now my question is i read somewhere it says the databse on the second
> server is read only...non writable? So what happens if i need to
> failover and make the secondary server live? Is it then only readable
> but unwritable? What good is that? Any ideas?>...or i just got it
> wrong?|||There is a great section in SQL Books on Line which describes in detail, how
to make a secondary database primary... including how to get the logins to
match... Search for Log shipping ...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"slycat" <slycat@.consultant.com> wrote in message
news:dec83278.0411091807.15bb247a@.posting.google.com...
> Hi, i think i'm just getting confused with all the reading. I have 2
> servers, A is live and B is doing nothing. I want to create some kind
> of warm standby so I looked at replication and log shipping. Repl
> seems to be kinda messy so i think i will go with log shipping.
> Database is around 2gigs and i can live with an interval of around
> 1/hr log ship.
> Now my question is i read somewhere it says the databse on the second
> server is read only...non writable? So what happens if i need to
> failover and make the secondary server live? Is it then only readable
> but unwritable? What good is that? Any ideas?>...or i just got it
> wrong?|||Log Shipping in SQL Server 2000, Part 1
http://www.winnetmag.com/Article/Ar...3056/23056.html
Log Shipping in SQL Server 2000, Part 2
http://www.winnetmag.com/Article/Ar...3230/23230.html
/Sukhdev

Question about Log Shipping: Secondary non-writable?

Hi, i think i'm just getting confused with all the reading. I have 2
servers, A is live and B is doing nothing. I want to create some kind
of warm standby so I looked at replication and log shipping. Repl
seems to be kinda messy so i think i will go with log shipping.
Database is around 2gigs and i can live with an interval of around
1/hr log ship.
Now my question is i read somewhere it says the databse on the second
server is read only...non writable? So what happens if i need to
failover and make the secondary server live? Is it then only readable
but unwritable? What good is that? Any ideas?>...or i just got it
wrong?The secondary is unwriteable as long as you are shipping logs. Once you
take it live, it becomes he 'real' database server and starts servicing
requests. Note that I am answering your questions on a conceptual level, if
you want the technical details of HOW that happens, that is for a follow-up
question.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"slycat" <slycat@.consultant.com> wrote in message
news:dec83278.0411091807.15bb247a@.posting.google.com...
> Hi, i think i'm just getting confused with all the reading. I have 2
> servers, A is live and B is doing nothing. I want to create some kind
> of warm standby so I looked at replication and log shipping. Repl
> seems to be kinda messy so i think i will go with log shipping.
> Database is around 2gigs and i can live with an interval of around
> 1/hr log ship.
> Now my question is i read somewhere it says the databse on the second
> server is read only...non writable? So what happens if i need to
> failover and make the secondary server live? Is it then only readable
> but unwritable? What good is that? Any ideas?>...or i just got it
> wrong?|||There is a great section in SQL Books on Line which describes in detail, how
to make a secondary database primary... including how to get the logins to
match... Search for Log shipping ...
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.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
"slycat" <slycat@.consultant.com> wrote in message
news:dec83278.0411091807.15bb247a@.posting.google.com...
> Hi, i think i'm just getting confused with all the reading. I have 2
> servers, A is live and B is doing nothing. I want to create some kind
> of warm standby so I looked at replication and log shipping. Repl
> seems to be kinda messy so i think i will go with log shipping.
> Database is around 2gigs and i can live with an interval of around
> 1/hr log ship.
> Now my question is i read somewhere it says the databse on the second
> server is read only...non writable? So what happens if i need to
> failover and make the secondary server live? Is it then only readable
> but unwritable? What good is that? Any ideas?>...or i just got it
> wrong?|||Log Shipping in SQL Server 2000, Part 1
http://www.winnetmag.com/Article/ArticleID/23056/23056.html
Log Shipping in SQL Server 2000, Part 2
http://www.winnetmag.com/Article/ArticleID/23230/23230.html
/Sukhdev

Question about how SQL Server decides when to auto-update statistics

I am reading the Microsoft article 'Statistical maintenance
functionality (autostats) in SQL Server'
(http://support.microsoft.com/kb/q195565/) and I'm wondering about this
part:
"NOTE: In addition to cardinality, the selectivity of the predicate
also affects AutoStats generation. This means that statistics may not
be updated afer every 500 modifications if cardinality were < 500 or
for every 20% of changes if cardinality were > 500. A scale up factor
(value ranges from 1 to 4, 1 and 4 inclusive) is generated depending on
the selectivity and a product of this factor and the number of changes
as obtained from the algorithm would be the actual number of
modifications required for AutoStats generation."
Does anyone know if a high selectivity means the factor is 1 or 4? Does
anyone know more about how that value is determined?
I'm also wondering about this part of the same article:
"Consider a second table, t2, that has a cardinality of 1,000. For
tables with greater than 500 rows, SQL Server will UPDATE STATISTICS
when (500 + 20 percent) changes have been made. Doing the math, 20
percent of 1,000 is 200, so you can expect to see AutoStat start after
approximately 700 modifications have been made to the table."
I don't understand why they say that AutoStats will execute after 700
modifications. 20 percent of 1000 rows is 200 rows, so wouldn't we
expect to see AutoStats after 200 rows, not 700 rows?
Thanks> Does anyone know if a high selectivity means the factor is 1 or 4? Does
> anyone know more about how that value is determined?
Does it really matter which is which? To the best of my knowledge you can't
see it anyway unless you decode the statblob. The point is that if the
selectivity is low you can get by with more rows changing before you have to
update the stats.

> I don't understand why they say that AutoStats will execute after 700
> modifications. 20 percent of 1000 rows is 200 rows, so wouldn't we
> expect to see AutoStats after 200 rows, not 700 rows?
It says 500 + 20%. If 20% is 200 rows then if you add that to 500 you get
700. Make sense?
If you are using sql 2005 these figures have chaged somewhat and you want to
ensure you are using the correct whitepaper.
Andrew J. Kelly SQL MVP
<pshroads@.gmail.com> wrote in message
news:1156534531.968254.118570@.75g2000cwc.googlegroups.com...
>I am reading the Microsoft article 'Statistical maintenance
> functionality (autostats) in SQL Server'
> (http://support.microsoft.com/kb/q195565/) and I'm wondering about this
> part:
> "NOTE: In addition to cardinality, the selectivity of the predicate
> also affects AutoStats generation. This means that statistics may not
> be updated afer every 500 modifications if cardinality were < 500 or
> for every 20% of changes if cardinality were > 500. A scale up factor
> (value ranges from 1 to 4, 1 and 4 inclusive) is generated depending on
> the selectivity and a product of this factor and the number of changes
> as obtained from the algorithm would be the actual number of
> modifications required for AutoStats generation."
> Does anyone know if a high selectivity means the factor is 1 or 4? Does
> anyone know more about how that value is determined?
> I'm also wondering about this part of the same article:
> "Consider a second table, t2, that has a cardinality of 1,000. For
> tables with greater than 500 rows, SQL Server will UPDATE STATISTICS
> when (500 + 20 percent) changes have been made. Doing the math, 20
> percent of 1,000 is 200, so you can expect to see AutoStat start after
> approximately 700 modifications have been made to the table."
> I don't understand why they say that AutoStats will execute after 700
> modifications. 20 percent of 1000 rows is 200 rows, so wouldn't we
> expect to see AutoStats after 200 rows, not 700 rows?
> Thanks
>

Question about how SQL Server decides when to auto-update statistics

I am reading the Microsoft article 'Statistical maintenance
functionality (autostats) in SQL Server'
(http://support.microsoft.com/kb/q195565/) and I'm wondering about this
part:
"NOTE: In addition to cardinality, the selectivity of the predicate
also affects AutoStats generation. This means that statistics may not
be updated afer every 500 modifications if cardinality were < 500 or
for every 20% of changes if cardinality were > 500. A scale up factor
(value ranges from 1 to 4, 1 and 4 inclusive) is generated depending on
the selectivity and a product of this factor and the number of changes
as obtained from the algorithm would be the actual number of
modifications required for AutoStats generation."
Does anyone know if a high selectivity means the factor is 1 or 4? Does
anyone know more about how that value is determined?
I'm also wondering about this part of the same article:
"Consider a second table, t2, that has a cardinality of 1,000. For
tables with greater than 500 rows, SQL Server will UPDATE STATISTICS
when (500 + 20 percent) changes have been made. Doing the math, 20
percent of 1,000 is 200, so you can expect to see AutoStat start after
approximately 700 modifications have been made to the table."
I don't understand why they say that AutoStats will execute after 700
modifications. 20 percent of 1000 rows is 200 rows, so wouldn't we
expect to see AutoStats after 200 rows, not 700 rows?
Thanks> Does anyone know if a high selectivity means the factor is 1 or 4? Does
> anyone know more about how that value is determined?
Does it really matter which is which? To the best of my knowledge you can't
see it anyway unless you decode the statblob. The point is that if the
selectivity is low you can get by with more rows changing before you have to
update the stats.
> I don't understand why they say that AutoStats will execute after 700
> modifications. 20 percent of 1000 rows is 200 rows, so wouldn't we
> expect to see AutoStats after 200 rows, not 700 rows?
It says 500 + 20%. If 20% is 200 rows then if you add that to 500 you get
700. Make sense?
If you are using sql 2005 these figures have chaged somewhat and you want to
ensure you are using the correct whitepaper.
--
Andrew J. Kelly SQL MVP
<pshroads@.gmail.com> wrote in message
news:1156534531.968254.118570@.75g2000cwc.googlegroups.com...
>I am reading the Microsoft article 'Statistical maintenance
> functionality (autostats) in SQL Server'
> (http://support.microsoft.com/kb/q195565/) and I'm wondering about this
> part:
> "NOTE: In addition to cardinality, the selectivity of the predicate
> also affects AutoStats generation. This means that statistics may not
> be updated afer every 500 modifications if cardinality were < 500 or
> for every 20% of changes if cardinality were > 500. A scale up factor
> (value ranges from 1 to 4, 1 and 4 inclusive) is generated depending on
> the selectivity and a product of this factor and the number of changes
> as obtained from the algorithm would be the actual number of
> modifications required for AutoStats generation."
> Does anyone know if a high selectivity means the factor is 1 or 4? Does
> anyone know more about how that value is determined?
> I'm also wondering about this part of the same article:
> "Consider a second table, t2, that has a cardinality of 1,000. For
> tables with greater than 500 rows, SQL Server will UPDATE STATISTICS
> when (500 + 20 percent) changes have been made. Doing the math, 20
> percent of 1,000 is 200, so you can expect to see AutoStat start after
> approximately 700 modifications have been made to the table."
> I don't understand why they say that AutoStats will execute after 700
> modifications. 20 percent of 1000 rows is 200 rows, so wouldn't we
> expect to see AutoStats after 200 rows, not 700 rows?
> Thanks
>

Question about configurations

I've been reading up on package configurations, but I'm not quite sure how to use them correctly. If I am developing a package, I want to connect to a testing server. Then, when it is working correctly, I want to connect to a production server. Are configurations a helpful way of doing this, or would it only be helpful if in the future, I need to make the packages reference a different server?

Hi Micheal,

That is exactly the use I want to make of configurations. I have been experimenting with registry and configuration file but neither seem to work. frankly I don't get it because I do exactly what I find in literature concerning this topic;

Keep me posted if you find the solution I'll do the same.

Greetings,

Paul.

|||

Configurations are all about taking the environment specific values out of a package and storing them elsewhere to make your packages portable. The configuration will then provide this information when you load the package.

Easy Package Configuration
(http://www.sqlis.com/default.aspx?26)

Jamie Thomson - SSIS Jibber Jabber : SSIS: Indirect configurations ROCK!
(http://blogs.conchango.com/jamiethomson/archive/2005/11/02/2342.aspx)

Keep Your Packages in the Dark
(http://www.sqlmag.com/Article/ArticleID/47688/sql_server_47688.html)

|||

Hi Michael,

You might find the solution in my thread Package Configuration using xml-file fails from yesterday. Jamie Thomson gave a very usefull answer.

Greetings,

Paul

Question about AWE.

SQL2K SP3
From reading BOL, to enable AWE, I should simply need to:
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', MyMax
RECONFIGURE
GO
And then start the SQL services. But a coworker of mine seems to think that
there's more to it then that. That SQL won't really be using AWE until we do
this something else. The best part is he's not sure what that something else
is. I think there's nothing else, but wanted to verify if I could.
TIA, ChrisRHi,Chris
http://www.sql-server-performance.com/awe_memory.asp
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:312ACADD-F513-4D8F-B5D8-F69C2D2E9138@.microsoft.com...
> SQL2K SP3
> From reading BOL, to enable AWE, I should simply need to:
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', MyMax
> RECONFIGURE
> GO
> And then start the SQL services. But a coworker of mine seems to think
> that
> there's more to it then that. That SQL won't really be using AWE until we
> do
> this something else. The best part is he's not sure what that something
> else
> is. I think there's nothing else, but wanted to verify if I could.
> TIA, ChrisR|||And also http://www.sqlservercentral.com/columnists/jsack/aweadventures.asp
See Lock Pages in memory priv.
Don't forget that if you install Sql2000sp4 you must get a hotfix otherwise
SQL will use half the memory (bug in the base SP4)
Paul
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eW7yW6TPGHA.3924@.TK2MSFTNGP14.phx.gbl...
> Hi,Chris
> http://www.sql-server-performance.com/awe_memory.asp
>
>
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:312ACADD-F513-4D8F-B5D8-F69C2D2E9138@.microsoft.com...
>> SQL2K SP3
>> From reading BOL, to enable AWE, I should simply need to:
>> sp_configure 'show advanced options', 1
>> RECONFIGURE
>> GO
>> sp_configure 'awe enabled', 1
>> RECONFIGURE
>> GO
>> sp_configure 'max server memory', MyMax
>> RECONFIGURE
>> GO
>> And then start the SQL services. But a coworker of mine seems to think
>> that
>> there's more to it then that. That SQL won't really be using AWE until we
>> do
>> this something else. The best part is he's not sure what that something
>> else
>> is. I think there's nothing else, but wanted to verify if I could.
>> TIA, ChrisR
>

Question about AWE.

SQL2K SP3
From reading BOL, to enable AWE, I should simply need to:
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', MyMax
RECONFIGURE
GO
And then start the SQL services. But a coworker of mine seems to think that
there's more to it then that. That SQL won't really be using AWE until we do
this something else. The best part is he's not sure what that something else
is. I think there's nothing else, but wanted to verify if I could.
TIA, ChrisRHi,Chris
http://www.sql-server-performance.com/awe_memory.asp
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:312ACADD-F513-4D8F-B5D8-F69C2D2E9138@.microsoft.com...
> SQL2K SP3
> From reading BOL, to enable AWE, I should simply need to:
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', MyMax
> RECONFIGURE
> GO
> And then start the SQL services. But a coworker of mine seems to think
> that
> there's more to it then that. That SQL won't really be using AWE until we
> do
> this something else. The best part is he's not sure what that something
> else
> is. I think there's nothing else, but wanted to verify if I could.
> TIA, ChrisR|||And also http://www.sqlservercentral.com/col...eadventures.asp
See Lock Pages in memory priv.
Don't forget that if you install Sql2000sp4 you must get a hotfix otherwise
SQL will use half the memory (bug in the base SP4)
Paul
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eW7yW6TPGHA.3924@.TK2MSFTNGP14.phx.gbl...
> Hi,Chris
> http://www.sql-server-performance.com/awe_memory.asp
>
>
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:312ACADD-F513-4D8F-B5D8-F69C2D2E9138@.microsoft.com...
>

Question about AWE.

SQL2K SP3
From reading BOL, to enable AWE, I should simply need to:
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', MyMax
RECONFIGURE
GO
And then start the SQL services. But a coworker of mine seems to think that
there's more to it then that. That SQL won't really be using AWE until we do
this something else. The best part is he's not sure what that something else
is. I think there's nothing else, but wanted to verify if I could.
TIA, ChrisR
Hi,Chris
http://www.sql-server-performance.com/awe_memory.asp
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:312ACADD-F513-4D8F-B5D8-F69C2D2E9138@.microsoft.com...
> SQL2K SP3
> From reading BOL, to enable AWE, I should simply need to:
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', MyMax
> RECONFIGURE
> GO
> And then start the SQL services. But a coworker of mine seems to think
> that
> there's more to it then that. That SQL won't really be using AWE until we
> do
> this something else. The best part is he's not sure what that something
> else
> is. I think there's nothing else, but wanted to verify if I could.
> TIA, ChrisR
|||And also http://www.sqlservercentral.com/colu...adventures.asp
See Lock Pages in memory priv.
Don't forget that if you install Sql2000sp4 you must get a hotfix otherwise
SQL will use half the memory (bug in the base SP4)
Paul
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eW7yW6TPGHA.3924@.TK2MSFTNGP14.phx.gbl...
> Hi,Chris
> http://www.sql-server-performance.com/awe_memory.asp
>
>
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:312ACADD-F513-4D8F-B5D8-F69C2D2E9138@.microsoft.com...
>

Question about Aliasing?

Heya,

While reading about aliasing using two different references, one author states that the aliasing is annotated using the key AS like in:
select...
FROM Emp as E1;

but in the other reference, the author states the key AS is not necessary, so the above query can be written instead as follows:
select...
FROM Emp E1

i am just wondering which one is correct? what MySQL/Oracle supports?

Many thankswhich one is correct depends on which database you're using

off the top of my head i can't remember which one requires AS (as opposed to it being optional)

besides, the sql reads better with AS, so i always throw it in, consequently i never get the syntax error when it's missing

helps?|||It works either way in Oracle or SQL Server. I'm not sure about mySQL. You're always safe using AS.

Question about "Data Transformation Services " : How to define myselfs query without DTS W

hi there, I have never use DTS before, now I am reading textbook for some special demand with DTS

the textbook not talk very much for the detail of skills. seems the easy way to finish this query is using DTS wizard.

but my requirement seems can't be done by DTS wizard.

here are my requirement below.

[move online Database to offline Database ]

1. the time of data preserve will have to reference separate firm's history data backup time ( for example, A company used to preserve data 6 months, and B company used to preserve data 12 months and so on..)

2. we will have only 2 kind of preserve time one is 6 months another is 12 months

3. The online DB only keeps 6 months data ( for example, when we do the DTS on 11/1 , we will only keep the data which from 5/1~10/31) , all data have to move to off-line DB except the past 6 months data

4. We will have to reference the history data preserve time to delete data after finished data movement

those requirement looks very diffcult for me because I have never use DTS before , can you please give me a simple example or maybe some article I can reference?

thank you very much and have a nice day

anyone ? please help...

|||

Hi,

Is there any field (such like datetime) in your datatable which can identify the time of the records. If so, you can use a query to specify the data to transfer. When you run your wizard, choose "use a query to transfer" item in "Specify table copy or query" step. Click on QueryBuilder button to build your filter sql statement and create your query criteria.(datetime filed) In this way, you can transform the data by datetime condition.

Hope that helps. Thanks.

|||

hi thank you is the only way ( run wizard) to finish this job?

could it be done by write a program? thank you

|||

Hi,

Of cause you can write programs to achieve your goal. Just filter the data according to the datetime condition and insert the data into your local(or backup) data server.But actually it's much complicated I think. Since we have a such a tool to ease our work, why don't we enjoy it

Thanks.