Estimating the Size and Growth of a Database / Table

I have been looking for a copy of a tool called the 'data sizer' that could
be found in the Microsoft BackOffice 4.5 Resource Kit. I have had no luck
tracking it down.
What I would like is a tool / script / stored proc that would allow me to
estimate how large a database would be and what the growth potential may be.
If anyone has anything they could share I would appreciate it.
Thanks,
SniperX
> What I would like is a tool / script / stored proc that would allow me to
> estimate how large a database would be and what the growth potential may
be.
> If anyone has anything they could share I would appreciate it.
If you have Books Online installed, see these topics:
Estimating the Size of a Table with a Clustered Index
Estimating the Size of a Table Without a Clustered Index
sql

Estimating the Size and Growth of a Database / Table

I have been looking for a copy of a tool called the 'data sizer' that could
be found in the Microsoft BackOffice 4.5 Resource Kit. I have had no luck
tracking it down.
What I would like is a tool / script / stored proc that would allow me to
estimate how large a database would be and what the growth potential may be.
If anyone has anything they could share I would appreciate it.
Thanks,
SniperX> What I would like is a tool / script / stored proc that would allow me to
> estimate how large a database would be and what the growth potential may
be.
> If anyone has anything they could share I would appreciate it.
If you have Books Online installed, see these topics:
Estimating the Size of a Table with a Clustered Index
Estimating the Size of a Table Without a Clustered Index

Estimating the Size and Growth of a Database / Table

I have been looking for a copy of a tool called the 'data sizer' that could
be found in the Microsoft BackOffice 4.5 Resource Kit. I have had no luck
tracking it down.
What I would like is a tool / script / stored proc that would allow me to
estimate how large a database would be and what the growth potential may be.
If anyone has anything they could share I would appreciate it.
Thanks,
SniperX> What I would like is a tool / script / stored proc that would allow me to
> estimate how large a database would be and what the growth potential may
be.
> If anyone has anything they could share I would appreciate it.
If you have Books Online installed, see these topics:
Estimating the Size of a Table with a Clustered Index
Estimating the Size of a Table Without a Clustered Index

Errors during building project with Deployment utility and configuration file

I am getting following error when "CreateDeploymentUtility" is set to true and I try building the solution. It tries to copy a file that already exits in \bin\Deployment folder. I am using Sept. CTP.

If I set "CreateDeploymentUtility" to false, there are no errors since it doesn't try copying the file. Any reason why this happens?
Error 1 System.ApplicationException: Could not copy file "C:\test\Source\ETLProcessing\PackageProject\test.dtsconfig" to the deployment utility output directory "C:\test\Source\ETLProcessing\PackageProject\bin\Deployment". > System.IO.IOException: The file 'C:\test\Source\ETLProcessing\PackageProject\bin\Deployment\test.dtsconfig' already exists. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CopyFiles(ICollection fileNames, String outputPath) End of inner exception stack trace at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CopyFiles(ICollection fileNames, String outputPath) at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CreateDeploymentUtility(IOutputWindow outputWindow) 0 0

Ignore the message above. The issue was related to having config file referenced in misc. folder within the project so when the project tries to rebuild it will try to copy config file twice. BIDS should add config file to project instead of just having it in file sytem. It's becomes an issue when you try to use source safe and the file is not part of the project.

|||I have had the same problem recently, and although the packages and configs are fine, the deployment manifest file is not created....at least in my case. This prevents easy deployment. Any reason for this? Workarounds?
Thanks,
Adrian Crawford|||The problem I had was relating to adding Config to a Misc folder. To solve the problem, I removed the config reference from Misc folder and rebuild the solution. I would suggest, deleting bin folder, making sure the config is not referenced within the project, and try rebuilding. This should solve your problem. Also make sure the config file is not locked, readonly, or opened by another process.|||

What do you mean by "make sure the config file is not referenced within the project"? I have created configurations and need to use them, but the manifest file isn't created...

Pedro Martins

Errors during building project with Deployment utility and configuration file

I am getting following error when "CreateDeploymentUtility" is set to true and I try building the solution. It tries to copy a file that already exits in \bin\Deployment folder. I am using Sept. CTP.

If I set "CreateDeploymentUtility" to false, there are no errors since it doesn't try copying the file. Any reason why this happens?
Error 1 System.ApplicationException: Could not copy file "C:\test\Source\ETLProcessing\PackageProject\test.dtsconfig" to the deployment utility output directory "C:\test\Source\ETLProcessing\PackageProject\bin\Deployment". > System.IO.IOException: The file 'C:\test\Source\ETLProcessing\PackageProject\bin\Deployment\test.dtsconfig' already exists. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CopyFiles(ICollection fileNames, String outputPath) End of inner exception stack trace at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CopyFiles(ICollection fileNames, String outputPath) at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CreateDeploymentUtility(IOutputWindow outputWindow) 0 0

Ignore the message above. The issue was related to having config file referenced in misc. folder within the project so when the project tries to rebuild it will try to copy config file twice. BIDS should add config file to project instead of just having it in file sytem. It's becomes an issue when you try to use source safe and the file is not part of the project.

|||I have had the same problem recently, and although the packages and configs are fine, the deployment manifest file is not created....at least in my case. This prevents easy deployment. Any reason for this? Workarounds?
Thanks,
Adrian Crawford
|||The problem I had was relating to adding Config to a Misc folder. To solve the problem, I removed the config reference from Misc folder and rebuild the solution. I would suggest, deleting bin folder, making sure the config is not referenced within the project, and try rebuilding. This should solve your problem. Also make sure the config file is not locked, readonly, or opened by another process.
|||

What do you mean by "make sure the config file is not referenced within the project"? I have created configurations and need to use them, but the manifest file isn't created...

Pedro Martins

Errors during building project with Deployment utility and configuration file

I am getting following error when "CreateDeploymentUtility" is set to true and I try building the solution. It tries to copy a file that already exits in \bin\Deployment folder. I am using Sept. CTP.

If I set "CreateDeploymentUtility" to false, there are no errors since it doesn't try copying the file. Any reason why this happens?
Error 1 System.ApplicationException: Could not copy file "C:\test\Source\ETLProcessing\PackageProject\test.dtsconfig" to the deployment utility output directory "C:\test\Source\ETLProcessing\PackageProject\bin\Deployment". > System.IO.IOException: The file 'C:\test\Source\ETLProcessing\PackageProject\bin\Deployment\test.dtsconfig' already exists. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CopyFiles(ICollection fileNames, String outputPath) End of inner exception stack trace at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CopyFiles(ICollection fileNames, String outputPath) at Microsoft.DataTransformationServices.Project.DataTransformationsProjectBuilder.CreateDeploymentUtility(IOutputWindow outputWindow) 0 0

Ignore the message above. The issue was related to having config file referenced in misc. folder within the project so when the project tries to rebuild it will try to copy config file twice. BIDS should add config file to project instead of just having it in file sytem. It's becomes an issue when you try to use source safe and the file is not part of the project.

|||I have had the same problem recently, and although the packages and configs are fine, the deployment manifest file is not created....at least in my case. This prevents easy deployment. Any reason for this? Workarounds?
Thanks,
Adrian Crawford
|||The problem I had was relating to adding Config to a Misc folder. To solve the problem, I removed the config reference from Misc folder and rebuild the solution. I would suggest, deleting bin folder, making sure the config is not referenced within the project, and try rebuilding. This should solve your problem. Also make sure the config file is not locked, readonly, or opened by another process.
|||

What do you mean by "make sure the config file is not referenced within the project"? I have created configurations and need to use them, but the manifest file isn't created...

Pedro Martins

Errors Copying Data Base

I'm trying to copy a data base from one server to another. Both servers are running 2005 MSDE, on Win 2k3, the target server is 64 bit.

I'm using the Copy Database function, and ultimately it fails with the error in the event viewer in the targe machine:

Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a, faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug? 0, fault address 0x0000000000027d0d.

I have tried both the Attach/Detach & the SMO method, and they both give me the same error. I have 'Repaired' the .NET framework on the target machine, with the same result.

Does anyone have any Suggestions? I really only need at this time to make one copy of the database.

Thanks

Phil

When you say "2005 MSDE", do you mean "2005 Express Edition"? You mentioned the target server is 64bit, is it IA64 or AMD64? My best guess is that you installed x86 version of SQL Server Express on AMD64 platform with WOW option.

Thanks,

Zhiqiang Feng

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

I have the x64 version of the Developer Edition of MS Sql Server 2005 installed on an AMD64 platform.

|||

More completely, the source server is a 32 bit machine, with MS Sql Server Developer Edition 2005, the target machine is the x64 configuration.

I have tried to initiate the transfer from both ends, i.e. the from the platform with the database pushing it to the platform without the DB, and from the platform without the DB, pulling it from the platform with the db

|||

Move the thread to the right alias. SSIS experts should be able to help out on your problem.

Thanks,

Zhiqiang Feng

This posting is provided "AS IS" with no warranties, and confers no rights.

|||the ssis transfer database task should help: http://msdn2.microsoft.com/en-us/library/ms141204.aspx

Error: The process could not bulk copy out of table '[dbo].[syncobj_0x3944323636373031]

SQL Server 2000 error message:

The process could not bulk copy out of table '[dbo].[syncobj_0x3944323636373031]'.

Snapshot replication was running fine up until last week. The e drive on the system failed. The server was rebooted and the drive returned. Since then the replication has failed. (e drive is the location of the database and log files)

The database is approx. 12 gig. I googled the error message an found several references to the drive being full. So I tried to map the replication to a different drive. The replication fails with the same error.

Also tried to drop and recreate the replication process. Still the same error.

Any other ideas?

TIA

Joel

You dont have enough permission to write to the destination database
or
you Sql service account dont have right to access the replication snapshot folder