Viewing 15 posts - 901 through 915 (of 2,488 total)
Sorry, forgot that sp_MSforeachtable only iterates through user objects. Try this instead,
SELECT db_name() as db , sObj.[name] as TblName , sInd.[name] as IndName , CONVERT(int, sInd.rowcnt) as...
--------------------
Colt 45 - the original point and click interface ![]()
August 23, 2005 at 7:49 pm
You can adjust the size of the commit by playing around with the 'Fetch Buffer Size' and 'Insert Batch Size' figures on the Options tab of the Datapump properties dialog....
--------------------
Colt 45 - the original point and click interface ![]()
August 23, 2005 at 5:48 pm
Who owns the job? Users cannot see/execute jobs that they don't own.
--------------------
Colt 45 - the original point and click interface ![]()
August 23, 2005 at 5:39 pm
Here's a quick way.
EXEC sp_MSforeachtable 'sp_spaceused @objname =''?'''
--------------------
Colt 45 - the original point and click interface ![]()
August 23, 2005 at 5:22 pm
Ok, here's a way I would probably end up doing it. This is pretty rough, I did do a bit a fiddling around to get some of the data to line...
--------------------
Colt 45 - the original point and click interface ![]()
August 23, 2005 at 4:17 am
As mentioned in my earlier post, the main bottleneck you seem to be encountering is transferring the files to the OLAP server. There is nothing that DTS, or SQL Server...
--------------------
Colt 45 - the original point and click interface ![]()
August 20, 2005 at 1:41 am
As mentioned in my earlier post, try using ROBOCOPY from the Windows Resource Kit.
--------------------
Colt 45 - the original point and click interface ![]()
August 19, 2005 at 5:41 am
Check the articles over at http://www.sqldts.com about changing the text file connection.
--------------------
Colt 45 - the original point and click interface ![]()
August 19, 2005 at 2:48 am
Is this data, log or both? Allocated space or used space?
Could be all you need to do is shrink the log file.
--------------------
Colt 45 - the original point and click interface ![]()
August 19, 2005 at 2:47 am
You could alter your stored procedure to accept the Job ID uniqueidentifier as a parameter.
Then in the job that calls the stored procedure, add the SQL Agent token [JOBID]. Then...
--------------------
Colt 45 - the original point and click interface ![]()
August 19, 2005 at 2:45 am
Best I've come up with is to put borders on the table in the report design. Make sure you use the thinnest line possible, otherwise you'll end up with huge...
--------------------
Colt 45 - the original point and click interface ![]()
August 19, 2005 at 2:42 am
As long as the structure of the tables is the same, you can replace TABLE_1 and TABLE_2 with your new tables names dynamically and everything will work great. If however...
--------------------
Colt 45 - the original point and click interface ![]()
August 19, 2005 at 2:37 am
Also, using Data Driven queries in the DTS packages will slow things down a lot. This causes the package to process data from the source in row-by-row method instead of...
--------------------
Colt 45 - the original point and click interface ![]()
August 19, 2005 at 2:22 am
Just to make sure I'm understanding what you've posted, the total time from steps 1 to 7 is 6 hours??
If so then I'd look at the main bottleneck in your process...
--------------------
Colt 45 - the original point and click interface ![]()
August 19, 2005 at 2:18 am
While Dan's comments are quite legitimate, you can use the WITH TABLERESULTS option on the DBCC SHOWCONTIG command to return the results in a table format. This make it easy...
--------------------
Colt 45 - the original point and click interface ![]()
August 18, 2005 at 11:43 pm
Viewing 15 posts - 901 through 915 (of 2,488 total)