Viewing 15 posts - 61 through 75 (of 318 total)
If you are asking if you can stop taking backups of the database once it is on the DEV server, of course. However, I would highly recommend you either...
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
September 9, 2011 at 12:54 pm
Are there any entries in the logs? Start with the SQL Error Logs and then move to the Windows Logs.
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
August 26, 2011 at 10:12 am
If you do not or cannot reinstall the OS - take a look at the following:
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
August 22, 2011 at 2:18 pm
This may be what you are looking for -
http://www-03.ibm.com/systems/i/software/access/index.html
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
August 5, 2011 at 10:33 am
My previous two employers paid a portion of both my cell phone plan and broadband internet. Recently I switched to Sprints mifi (all couriers seem to have this option...
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
July 29, 2011 at 3:33 pm
Use Master
Alter Database [insert db name here]
SET SINGLE_USER With ROLLBACK IMMEDIATE
RESTORE DATABASE [insert db name here] FROM DISK = 'E:\backup\insert db backup name here.bak'
WITH REPLACE
GO
Tweak as needed.
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
July 29, 2011 at 3:30 pm
Not to nitpick, but even the article referenced stated - "On a computer that has a multicore processor, you may be unable to install SQL Server 2005"
The optimal word being...
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
July 29, 2011 at 7:17 am
Most likely you did not completely uninstall SQL Server. There are numerous sites if you do a Google search that go into great detail of exactly what and where...
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
July 21, 2011 at 12:44 pm
Just a guess, but you may have hit the maximum job history log size.
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
July 21, 2011 at 12:40 pm
What are you attempting to do? Rebuild the master database? Change licensing? Collation?
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
July 21, 2011 at 12:36 pm
Are you accessing the Maintenance Plan wizard/tool via SQL 2000 Enterprise Manager or are you attempting to create a plan using SQL 2005 Management Studio remotely?
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
July 18, 2011 at 1:14 pm
Unfortunately you must do a step upgrade when SQL 7 is involved.
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
July 14, 2011 at 1:19 pm
By chance is the mystery job actually associated with a old Maintenance Plan?
Check that Job ID against the sysmaintplan_subplans table
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
July 14, 2011 at 1:16 pm
Could you post the solution for others that may have a similar issue.
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
July 14, 2011 at 7:18 am
Please attempt to use the IP address instead of the server name.
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
July 13, 2011 at 6:57 am
Viewing 15 posts - 61 through 75 (of 318 total)