Recover data from yesterday

Hi,
I'm not a database manager,
I have to recover the old database instead of the actual.
I backed up the old one from a tape backup.
Do i have just to rename the existing one and copy the one
that i want in the same folder.
People told me that there was no change between these two
version except that someone erase a folder.
Thank...
If you are talking about SQL Database (instead of MDMArch'd Analysis
Services database) ,YOu may restore the SQL database using the restore
wizard, but
1. Restore as a DIFFERENT database name and
2. on the second tab, choose DIFFERENT PHYSICAL FILENAMES/Locations for
each file so you will not overwrite the good, current version of the
database...
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
"Alain" <anonymous@.discussions.microsoft.com> wrote in message
news:233501c4aca0$2e00dd90$a601280a@.phx.gbl...
> Hi,
> I'm not a database manager,
> I have to recover the old database instead of the actual.
> I backed up the old one from a tape backup.
> Do i have just to rename the existing one and copy the one
> that i want in the same folder.
> People told me that there was no change between these two
> version except that someone erase a folder.
> Thank...

Records not commiting - please help!

So, I have this SSIS package that basically moves records from one table into another table in the same DB. I’m running it on the actual server and everything seems to work. The data-flow task lights up yellow and visual studio increments the number of records passed through as if they were running perfectly. However, when I go to look at the data,it’s not in there! There are no errors reported ad the event log doesn’t show anything that would lead me to think anything went wrong. Anyone ever run into this issue? I’m wracking my brain on this one and am completely stumped. Any help would really be appreciated

Do you wait until the process completes (goes green) to look for the records?|||

I've let it go all the way to the end and tried to look at the data while the move was hapening. I've played with all the OLE DB destination options as well with no luck. I've had batch sizes of anywhere from 1 to 1000 with no luck. SQL server activity monitor lists the bulk insert but it never leaves the "runnable" state.

I am using the OLE DB data source and destination and have one data conversion transform task between them.

|||Are you sure the records are valid? Double click on the OLE DB Destination and select "Error output" and ensure that it is set to "Fail component" instead of "Ignore failure."|||

Try using a destination table which has no rows. Then run your package, and see if the destination table has any rows now. That will help you identify if rows are not being inserted at all, or were inserted but some other failure happened.

|||

so, the destination table's totally empty. I ran the package all the way through and it's still not working!!! I can tell somethings happening since my drive's filling up as the thing trudges along. Very, very irritating~

|||

JimiTooCool wrote:

so, the destination table's totally empty. I ran the package all the way through and it's still not working!!! I can tell somethings happening since my drive's filling up as the thing trudges along. Very, very irritating~

Did you make sure that the error handling of the OLE DB destination was set to "Fail component"?

Records newer than 90 minutes (smalldatetime)

Hi,

I have a table in SQLServer2000 where e.g. the actual time is insert for
every record (smalldatetime). But how do I select every records newer
than 90 minutes?

/ChrisOn Mon, 08 Nov 2004 21:24:33 +0100, Chris wrote:

>Hi,
>I have a table in SQLServer2000 where e.g. the actual time is insert for
>every record (smalldatetime). But how do I select every records newer
>than 90 minutes?
>/Chris

Hi Chris,

SELECT Column1, Column2, ..., ColumnN
FROM MyTable
WHERE InsertionTime > DATEADD(minute, -90, CURRENT_TIMESTAMP)

Best, Hugo
--

(Remove _NO_ and _SPAM_ to get my e-mail address)|||On Mon, 08 Nov 2004 21:24:33 +0100, Chris wrote:

> Hi,
> I have a table in SQLServer2000 where e.g. the actual time is insert for
> every record (smalldatetime). But how do I select every records newer
> than 90 minutes?
> /Chris

SELECT * FROM Tbl WHERE DateDiff(m,time_column,GetDate()) BETWEEN 0 AND 90

And you'd better have an index on your time_column.|||On Mon, 8 Nov 2004 16:45:45 -0500, Ross Presser wrote:

>On Mon, 08 Nov 2004 21:24:33 +0100, Chris wrote:
>> Hi,
>>
>> I have a table in SQLServer2000 where e.g. the actual time is insert for
>> every record (smalldatetime). But how do I select every records newer
>> than 90 minutes?
>>
>> /Chris
>SELECT * FROM Tbl WHERE DateDiff(m,time_column,GetDate()) BETWEEN 0 AND 90
>And you'd better have an index on your time_column.

Hi Ross,

As far as I know, that index won't be used in your query, since the
time_column is embedded in a function call. You'd have to have the
time_column all by itself at one side of a comparison operator (like in my
query) for the index to be useful.

Best, Hugo
--

(Remove _NO_ and _SPAM_ to get my e-mail address)|||Hugo Kornelis <hugo@.pe_NO_rFact.in_SPAM_fo> wrote in
news:kpuvo0l9uegi5iuute1h7rte13cp34dsh6@.4ax.com:

> On Mon, 8 Nov 2004 16:45:45 -0500, Ross Presser wrote:
>>On Mon, 08 Nov 2004 21:24:33 +0100, Chris wrote:
>>
>>> Hi,
>>>
>>> I have a table in SQLServer2000 where e.g. the actual time is insert
>>> for every record (smalldatetime). But how do I select every records
>>> newer than 90 minutes?
>>>
>>> /Chris
>>
>>SELECT * FROM Tbl WHERE DateDiff(m,time_column,GetDate()) BETWEEN 0
>>AND 90
>>
>>And you'd better have an index on your time_column.
> Hi Ross,
> As far as I know, that index won't be used in your query, since the
> time_column is embedded in a function call. You'd have to have the
> time_column all by itself at one side of a comparison operator (like
> in my query) for the index to be useful.
> Best, Hugo

Thank you for clarifying my fuzzy thinking, Hugo. Your query is much better
in that respect.