Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
bashka_abdyli
Starting Member
15 Posts |
 Posted - 2003-08-04 : 02:12:56
|
| First I am using merge replication and sometimes it is nessesary to make a big delete or update for example 500 000 rows is it possible to send this to subscribers just like stored procedure if not which is the best way to do so,Second I have a table "transactions" with 20,000,000 rows is it better to seperate into this tables"deposits", "withdrawals", "transfers", "loans", "payments" or to keep just in one tablethanks in advance |
|
|
SqlStar
Posting Yak Master
121 Posts |
Posted - 2003-08-04 : 10:08:30
|
Hi, quote:
I have a table "transactions" with 20,000,000 rows is it better to seperate into this tables"deposits", "withdrawals", "transfers", "loans", "payments" or to keep just in one table
If u have any "TYPE" column for separating data,u can create separate table for each type.otherwise,data classification is very...tedious job.Think and do that.If u create separate table for each type, Please use those tables only.Just refer this old table, wherever u want.Bye...":-) IT Knowledge is power :-)" |
 |
|
|
X002548
Not Just a Number
15586 Posts |
Posted - 2003-08-04 : 10:20:14
|
quote:
Originally posted by bashka_abdyli
First I am using merge replication and sometimes it is nessesary to make a big delete or update for example 500 000 rows is it possible to send this to subscribers just like stored procedure if not which is the best way to do so,
Don't use replication?quote:
Second I have a table "transactions" with 20,000,000 rows is it better to seperate into this tables"deposits", "withdrawals", "transfers", "loans", "payments" or to keep just in one table
Depends on what you're going to do with it...How often do you query against it...I bet it's mostly inserts and selects, with no deletes or updates...How much "current" data do you query against? How would you define current...I would say, move what you don't access often to history, and keep what you need in a smaller "current" table...Brett8-)SELECT POST=NewId() |
|
|
|
|
|
|
|
|
two questions