with db mirroring, every action on the primary database is sent to the mirror db.

It is not active, so no one else can tamper with it.

Keep in mind a backup file can contain more than one backup !

Are you creating log backups using the NOINIT parameter ? That's the way you can add a backup...

check the ms website for more info and prereqs.

http://www.microsoft.com/sql/solutions/migration/oracle/default.mspx

and

http://www.microsoft.com/sql/techinfo/whitepapers/MigrOracleSQL2005.mspx

That should be ok.

Yep, checking is what makes this job worth the while :hehe:

Chris Morris (10/3/2008)

---

Had to try it, guys...

[font="Courier New"]DECLARE @StringIn VARCHAR(200), @StringOut VARCHAR(200)

SET @StringIn = 'The Quick Brown Fox Jumps Over The Lazy Dog.'

SET @StringOut = ''

SELECT @StringOut = @StringOut +...

There is a MS white paper called "MS WP DatabaseMirroring.doc"

It contains a nice overview of all sqlserver replication techniques and when to use them.

This is a "hear say" :the only...

Our best friend ... BOL ... guided me on this one :w00t:

/*

http://www.sqlservercentral.com/Forums/Topic579917-338-1.aspx

ROT13 ref http://en.wikipedia.org/wiki/ROT13

*/

CREATE FUNCTION dbo.ufn_ROT13 (@inputvar varchar(128))

RETURNS varchar(128)

AS

/*

declare @inputvar varchar(128)

set @inputvar = 'abcdefghijklmnopqrstuvwxyz'

select @inputvar = @inputvar + upper(@inputvar)...

mtassin (10/2/2008)

---

The problem with this plan is that CLR doesn't work on SQL 2000.

Yes this is the SQL 2005 forum. But... what I'm working on needs to run on...

As I've read from our "SQL Obi-wan Kenobis" (Jeff Moden & Matt Miller 😉 ) this would be a typical case to use a CLR module.

Don't use the xp,...

Your problem is you use

NestedSel.*

This part already contains a mkt_rate column.

You generate a new mkt_rate column right next using

mkt_rate =...

Nice ... the N-th datetime solutions payback time :hehe:

Just for correctness ...

can you elaborate and split your bigint into the date part and the timepart ?

1196100822809

1196 = NoDays

10= HH

08 =...

how about this:

Declare @mybigint bigint

set @mybigint =

convert(bigint,replace(replace(replace(replace(convert(char(23), getdate(), 121),'-',''),':',''),'.',''),' ',''))

print @mybigint

declare @mychar char(23)

Select @mychar = convert(char(23), @mybigint)

Select @mychar = substring(@mychar,1,4) + '-' + substring(@mychar,5,2) + '-' +...

You could add new filegroups and move your data to the appropriate filegroup by moving the clustering indexes.

Also keep in mind you may also have to move non clustering...

I haven't performed it on a replicated database.

Keep in mind, you can only shrink a log file up to the 'last' active chunk it uses.

Maybe you'll have redo the shrink...