Brian doesn't want to control which objects go to which file.  He only wants to ensure that data is split evenly across the files.  Having multiple files within the same...

Michelle

That's just too tricky.  If you don't have somewhere you can test this before you do it for real, then a large part of it is going to be keeping...

Michelle

I wouldn't risk trying to restore the system databases.  That's why I suggested scripting out logins, jobs and so on, so that you can do a clean install and then...

Adam

This will work in SQL Server 2005 as well:

CREATE PROCEDURE MyProc @colname sysname

AS

SELECT 'select [' + column_name + '] from [' + table_schema + '].[' + table_name + ']'

FROM information_schema.columns

WHERE column_name = @colname

GO

Call it like this:

Charlie

I'm not sure how you got any results at all from that query, but never mind - try this:

--Table

CREATE TABLE MyTable (sampleno INT,  workcode decimal(5, 2), result INT)

--Data

INSERT INTO MyTable VALUES (211,  33,  50)

INSERT INTO MyTable VALUES (211,   33.01,  51)

INSERT INTO MyTable VALUES (211,  33.02,  54)

INSERT INTO MyTable VALUES (211,  33.03,  32)

INSERT INTO MyTable VALUES (212,  33,  23)

INSERT INTO MyTable VALUES (212,  33.01,  34)

INSERT INTO MyTable VALUES (212,  33.02,  24)...

Brian

I suppose one way to do it would be to create twelve new files in a new filegroup.  Then you can drop the clustered index of each table and recreate...

Adam

It sounds like poor database design to me - are we allowed to know why they want to do this?

Anyway, to answer your question.  How about creating a table with...

BK

Use the sp_helplogins stored procedure to get a list of how logins map to users and roles in databases.  The query below will return a list of logins and what...

Kenneth

Some DDL would have been helpful.  Still, here's a guess.  Despite the title of the thread, you don't need a loop - you can do it with a set-based query.

http://support.microsoft.com/kb/274750

Alex

That behaviour is typical of SQL Server.  It grabs all the memory it can and only gives it back if another process requires it.  If you find that there's contention...

Could it be that you have a case-sensitive collation, so that when you do SELECT * FROM sysobjects WHERE name = 'MYTABLE' and xtype = 'U', it doesn't return anything...

SELECT

[name]

      ,[enabled]

      ,[description]

FROM [msdb].[dbo].[sysjobs]