Viewing 15 posts - 121 through 135 (of 346 total)
Difficult to say what the issue is.
If you want to look at hardware then do you have separate disks for the tr log and are backups taken to a different...
Cursors never.
DTS - only when needed and never to control.
May 25, 2009 at 2:13 am
Those should help but really need to know where the issues are.
Can you materialise the datasets you are using and maybe update them from triggers.
It looks like the table structure...
Cursors never.
DTS - only when needed and never to control.
May 25, 2009 at 2:03 am
Looks like the loop is just splitting up comma delimitted lists from @t2
This would mean you don't need the identity.
insert @t3
select distinct SUBSTRING(Column1, 1,PATINDEX('%,%',Column1))
from @t2
while @@ROWCOUNT 0
begin
update @t2
set Column1...
Cursors never.
DTS - only when needed and never to control.
May 25, 2009 at 2:01 am
Assume you've dealt with indexing and such
A few obvious comments
Could you change union to union all?
in (select DISTINCT Column1 from @t3)
Could you ensure unique values in @t3 rather than using...
Cursors never.
DTS - only when needed and never to control.
May 25, 2009 at 1:42 am
A linked server is just a method of querying the remote server.
You have to issue sql statements to extract data
select *
from LinkedServer.dbname.dbo.tblname
where .....
it doesn't do anything automatically with regards to...
Cursors never.
DTS - only when needed and never to control.
March 2, 2009 at 6:08 am
If there's nothing to say when a row is updated then you are stuck with transferring the whole table (or checksums) and checking it.
Not feasible if the table is large...
Cursors never.
DTS - only when needed and never to control.
March 2, 2009 at 3:48 am
So you are updating your local copy of the database from the server?
Does the table have anything to say when a row was updated? A last updated column, a timestamp,...
Cursors never.
DTS - only when needed and never to control.
March 2, 2009 at 2:47 am
>> always the same columns is returned
>> q.*
Both dangerous statements.
Does q have a simple PK?
If so I would return the those values then join to q to get the data.
Whether...
Cursors never.
DTS - only when needed and never to control.
March 1, 2009 at 7:40 pm
Are you asying that you have data on your local machine which is being accessed from the server to support queries (to avoid data duplication)?
I would go back to your...
Cursors never.
DTS - only when needed and never to control.
March 1, 2009 at 6:50 pm
Can you create a partitioned view.
No idea if this is still available in v2005 or how it's supported by standard edition.
Note it this is still on one disk you will...
Cursors never.
DTS - only when needed and never to control.
March 1, 2009 at 6:45 pm
Your only problem is the foreign key so the options are:
1. Support the integrity programatically - maybe by a trigger.
2. A single referenced table with possibly a lot of attributes...
Cursors never.
DTS - only when needed and never to control.
March 1, 2009 at 6:31 pm
I do this using sql fom the table definitions.
Create an SSIS package to import the data to a staging table (xml is created from a template and the source/destination columns...
Cursors never.
DTS - only when needed and never to control.
March 1, 2009 at 6:15 pm
Changing the collation of the user databases won't help - it only affects new tables that use the default collation. You would need to change the collation of all the...
Cursors never.
DTS - only when needed and never to control.
March 1, 2009 at 6:08 pm
Have a look at what it generates.
You will have two tables.
One will have a foreign key that references the other
create table manager
(
manager_id int
)
create table player
(
player_id int ,
manager_id int ,
foreign key...
Cursors never.
DTS - only when needed and never to control.
March 1, 2009 at 5:56 pm
Viewing 15 posts - 121 through 135 (of 346 total)