DECLARE @a VARCHAR(50)

SET @a = 'ABC:123;TEST:pq'

SELECT PATINDEX('%:%', @a) AS Col, PATINDEX('%;%', @a) AS SCol, SUBSTRING(@a, 4 + 1, 8 - (4 + 1)) AS Extract

DECLARE @b-2 table (a varchar(50))

INSERT INTO...

Ok, then list & loop.

I guess in your proc you have <many> statements like

SELECT whatever from dbo.table where col = @p1 and col2 = @p2

Just add an extra join to your temp table with...

GilaMonster (9/21/2011)

---

Ninja's_RGR'us (9/21/2011)

---

You can use the default trace to see at what time the db starts growing and then you can zoom in on the jobs that run at that...

You froze the server or your local machine (please tell...

Don't have any,...

Jim Murphy (9/21/2011)

---

Stefan Krzywicki (9/21/2011)

---

A friend of mine posted this and I had to repost it here.

A DBA walks into a NOSQL bar, but he turns around and leaves. He...

Of course this can change. It's an estimate and if there's contention the end time will change.

There are also start & end process that can screw this up (create...

GilaMonster (9/21/2011)

---

Monitor SQLPerf(LogSpace). That will give you a view of used space.

If it keeps growing check open transactions (while it's growing) and see if a checkpoint helps.

I have never...

Can't use tally here.

Copy the SP you're copy.

Add a temp table at the top and fill it with what you need to process.

Then join that table to all subsequent steps...

Depends on the queries.

The real issue is when you need to join / filter based on data that's in both servers. Otherwise the server can fully optimize...

sqluser_8119 (9/21/2011)

---

I have a sql server that has around 20,000 jobs that need to be migrated to another server. Both boxes are sql server 2005 SE. Obviously scripting the jobs...

NJ-DBA (9/21/2011)

---

Henrico Bekker (9/21/2011)

---

try using the following:

use master

go

SELECT

percent_complete AS ‘PctComplete’,

start_time AS ‘StartTime’,

command AS...

1000 rows / sec is still craply slow. But if you're happy... ;-).

For 19 seconds, I'd expect to process at the very least 1 M rows.

I've never seen a tool that an replace an great DBA.

Bad / Mediocre maybe, but then again I wouldn't want him using a tool that can provide wrong solutions since...