Tag Info

Hot answers tagged

7

What you're trying to do would leave the database in a (transactionally) inconsistent state, hence it isn't possible. The Partial Database Availability whitepaper is a useful reference guide and includes an example of how to check whether a particular table or file is online. If your data access were through stored procedures, you could relatively easily ...


5

60.000 files and 50 GB should be absolutely no problem. You might want to read "Special Consideration for Large Environments". A challenge could be to come up with a recovery plan.


5

I finally found how to do it. I've found some very old backups. The data changed meanwhile, and it was important to have an up-to-date version of this data, which meant that it wasn't possible to just restore the old backup. Instead, I did the following, thanks to Michael Eklöf on ServerFault: Copy the current .mdf and .ldf files. List the filegroups of ...


4

To use FILESTREAM, it has to be configured at the OS and instance level. At the OS level, FILESTREAM is enabled either during the installation of SQL Server 2008 or by running SQL Server Configuration Manager. Once FILESTREAM has been setup, you have to create a FILESTREAM filegroup. You then have to create a data container in the FILESTREAM filegroup. Once ...


3

this isn't exactly how filestream and filetables work, you can't specify the name of an existing share as SQL server will try and create the share that you specify in SQL Server Configuration Manager. This is because the share is not mapped directly to a folder on the filesystem like a normal share, but an NTFS data container that lives in the filestream ...


2

So the linefeed before peas and dhdhjsk should be skipped but the linefeed before save is part of the data. Which linefeeds should be skipped and which are part of the data? I think such a format is very error prone and should be avoided. Perhaps you can do it the following way but I did not verify this define "," as the physical record separator join ...


2

It seems like insufficient info to tell something definitely. For example, are you deleting through Transact-SQL or through Win32API, etc. The FILESTREAM data is not deleted immediately from file system because SQL Server transaction logging under full and bulk recovery models permit the crash recovery. Have you deleted with CHECKPOINT delete from ...


2

Actually you can put as many files as you want in a file group. Basically file group feature included in sql server so that you can archive your organization data properly and can query the data efficiently. Its also depend on the hard disk space on server and configuration that which raid model you use for data storage.


2

The error seems to point at the SQL Server Service account not being able to access the filestream data. Try to change the SQL Server Service account using the SQL Server Configuration Manager (NOT the Windows Services manager!) to one of the build in accounts. Then change it right back to the original account (you will need to know the password here!). ...


2

Just as caveat it is best not to disturb the physical files involved with FILESTREAM for a database. Below are a few good links on the architecture: Paul Randal White Paper - FILESTREAM Storage Paul Randal Blog Post - FILESTREAM directory structure As quoted from Paul's blog post above: The FILESTREAM file names are actually the log-sequence number ...


1

You need to have "Allow remote clients access to FILESTREAM data" selected as shown below : Also, you need to leave the windows share as a Globalroot path and manage permissions through table properties, not Windows share properties. Refer to : Prerequisites for FileTable


1

In short you can't. You would have to restore the entire database to another machine, then copy the needed file from the restored machine and put it into place on the production server. Single object restores and single row restores (which is what restoring a single file effectively is) have never been supported via the native tools.


1

FindNextFile is a Windows API call, so what's happening is the backup process is enumerating all the files in the FILESTREAM folder and backing them up. The error message indicates that the operating system cannot read the file system; this indicates, at least to me, that the file/folder structure on disk is corrupt. There would be a different error returned ...



Only top voted, non community-wiki answers of a minimum length are eligible