Viewing 15 posts - 301 through 315 (of 2,488 total)
That is normal behaviour. SQL Server will consume as much memory as it needs, mostly for caching data. It will hold onto that memory until the operating system demands it...
--------------------
Colt 45 - the original point and click interface ![]()
May 28, 2007 at 6:53 am
Yes you may be able to recover some of the transactions in the LDF file. What you need to do is perform a "Tail Log" backup. Refer to this KB...
--------------------
Colt 45 - the original point and click interface ![]()
May 27, 2007 at 11:19 pm
Are you able to access the file via a shared folder? If so, then the regular datapump will work fine.
If not, and you definitely can't save the file locally (even...
--------------------
Colt 45 - the original point and click interface ![]()
May 22, 2007 at 7:01 pm
One thing thats not clear here is what version of VMWare we're talking about. The flagship product VMWare ESX Server, does get down and dirty with the hardware and allows...
--------------------
Colt 45 - the original point and click interface ![]()
May 22, 2007 at 12:30 am
Were you able to setup a datapump to import the file?
--------------------
Colt 45 - the original point and click interface ![]()
May 22, 2007 at 12:22 am
Also, just to throw oil on the fire, the number of Parameter values depends on what delivery method and other options are selected.
--------------------
Colt 45 - the original point and click interface ![]()
May 21, 2007 at 3:07 am
Was this package running before your upgrade to SP2?
Seen a number of these type of errors occurring after SP2 was applied. File permissions don't seem to be the problem.
Are you...
--------------------
Colt 45 - the original point and click interface ![]()
May 20, 2007 at 11:59 pm
That would be possible particularly in MSDE and SQL Express as they close the database when there a no active connections. In SQL Server if the database is set to...
--------------------
Colt 45 - the original point and click interface ![]()
May 20, 2007 at 9:58 pm
The important part is not really how its done, just that each process is seperate and unrelated to the other processes that just happen to make up Log Shipping. This...
--------------------
Colt 45 - the original point and click interface ![]()
May 20, 2007 at 9:37 pm
In the DTS package, after the ActiveScript task have a Text Source connection then have a SQL Server connection and put a datapump task between the two connections.
--------------------
Colt 45 - the original point and click interface ![]()
May 19, 2007 at 6:45 pm
What account does the SQL Services run under? When you execute a DTS package manually it will use your login credentials. Executing from a stored procedure/schedule job/etc... it will run...
--------------------
Colt 45 - the original point and click interface ![]()
May 19, 2007 at 6:44 pm
Not too sure of the specific coding, but I think the best bet would be to have an ActiveScript task that performs a HTTP GET and saves the file locally....
--------------------
Colt 45 - the original point and click interface ![]()
May 17, 2007 at 10:44 pm
Log Shipping itself does not have automatic failover. You will need to "bolt on" something extra to have automatic failover. Even then it still miight not be automatic. What happens...
--------------------
Colt 45 - the original point and click interface ![]()
May 17, 2007 at 6:29 pm
Have a look over at http://www.sqldts.com they'll have a few examples.
--------------------
Colt 45 - the original point and click interface ![]()
May 16, 2007 at 6:19 pm
To execute a windows process on another server you'll need to use a tool like PSEXEC from Sysinternals.
--------------------
Colt 45 - the original point and click interface ![]()
May 16, 2007 at 6:12 pm
Viewing 15 posts - 301 through 315 (of 2,488 total)