drawbacks of Saving documents to Sql server

Hi all,
..Net 1.1
Sql server 2000
i am working on a document managment module of my application, all i want to
do here is save the documents uplaoded by the user from my winforms over
webservices application\ webforms applicatoin to sql server 2000. I have been
told saving it on the webserver's file system might be a better way but seems
that microsft is gong more towars saving everthing in sql server. So my
question to the gurus out there is
1. does any one really have any hands on experience saving documents to sql
server 2000 and if so please tell me if u have any kind of performance issues
with this.
2. i was told that sql server is kind of a little slow in streaming out the
documents from the database, expecially bigger ones when compared to the
retriving it from the web server's file system, is this true ?
3. please tell me any other problesm that u might have faced when saving\
retriving files from the database.
4. is sql server 2005 any better in saving and retriving documents from the
database.
thanks
sameer
Answered in .programming.
Please do not post the same message independently to multiple newsgroups.
sql

drawbacks of Saving documents to Sql server

Hi all,
.Net 1.1
Sql server 2000
i am working on a document managment module of my application, all i want to
do here is save the documents uplaoded by the user from my winforms over
webservices application\ webforms applicatoin to sql server 2000. I have been
told saving it on the webserver's file system might be a better way but seems
that microsft is gong more towars saving everthing in sql server. So my
question to the gurus out there is
1. does any one really have any hands on experience saving documents to sql
server 2000 and if so please tell me if u have any kind of performance issues
with this.
2. i was told that sql server is kind of a little slow in streaming out the
documents from the database, expecially bigger ones when compared to the
retriving it from the web server's file system, is this true ?
3. please tell me any other problesm that u might have faced when saving\
retriving files from the database.
4. is sql server 2005 any better in saving and retriving documents from the
database.
thanks
sameerAnswered in .programming.
Please do not post the same message independently to multiple newsgroups.

drawbacks of Saving documents to Sql server

Hi all,
.Net 1.1
Sql server 2000
i am working on a document managment module of my application, all i want to
do here is save the documents uplaoded by the user from my winforms over
webservices application\ webforms applicatoin to sql server 2000. I have bee
n
told saving it on the webserver's file system might be a better way but seem
s
that microsft is gong more towars saving everthing in sql server. So my
question to the gurus out there is
1. does any one really have any hands on experience saving documents to sql
server 2000 and if so please tell me if u have any kind of performance issue
s
with this.
2. i was told that sql server is kind of a little slow in streaming out the
documents from the database, expecially bigger ones when compared to the
retriving it from the web server's file system, is this true ?
3. please tell me any other problesm that u might have faced when saving\
retriving files from the database.
4. is sql server 2005 any better in saving and retriving documents from the
database.
thanks
sameerAnswered in .programming.
Please do not post the same message independently to multiple newsgroups.

DR Testing

Hi all -
I am working with the DBA's to do some DR testing to see how to recover the
Master db if it became corrupted or unusable. We found a bunch of links
about doing this, but nothing seems to work. We used the SQL Server 2005
setup.exe method that MS seems to indicate is the way to do it, but it bombs
with no error and does nothing. We then just ran setup and went through the
steps, and when it does it's pre-installation checking, it complains that we
are trying to change the edition. I am guessing at this point this is
because we installed SP2, and are trying to recover using the non-SP CD.
Since MS does not allow slipstreaming service packs with SQL Server, how are
you supposed to do this?
Thanks for any info anyone can provide
MattHello Matt,
Here you go:
http://msdn2.microsoft.com/en-us/library/ms190679.aspx
http://msdn2.microsoft.com/en-us/library/ms175535.aspx
http://msdn2.microsoft.com/en-us/library/ms190190.aspx
http://msdn2.microsoft.com/en-us/library/ms191431.aspx
Cheers!
MB
"md" <someone@.microsoft.com> wrote in message
news:uDac9PDfHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Hi all -
> I am working with the DBA's to do some DR testing to see how to recover
> the Master db if it became corrupted or unusable. We found a bunch of
> links about doing this, but nothing seems to work. We used the SQL Server
> 2005 setup.exe method that MS seems to indicate is the way to do it, but
> it bombs with no error and does nothing. We then just ran setup and went
> through the steps, and when it does it's pre-installation checking, it
> complains that we are trying to change the edition. I am guessing at this
> point this is because we installed SP2, and are trying to recover using
> the non-SP CD. Since MS does not allow slipstreaming service packs with
> SQL Server, how are you supposed to do this?
> Thanks for any info anyone can provide
> Matt
>|||Thanks MB. We had found some of these already, but not all. I forwarded them
to the DBA to take a look.
Thanks again
Matt
"MB" <MB@.MB.com> wrote in message
news:%23K4VhcDfHHA.4916@.TK2MSFTNGP06.phx.gbl...
> Hello Matt,
> Here you go:
> http://msdn2.microsoft.com/en-us/library/ms190679.aspx
> http://msdn2.microsoft.com/en-us/library/ms175535.aspx
> http://msdn2.microsoft.com/en-us/library/ms190190.aspx
> http://msdn2.microsoft.com/en-us/library/ms191431.aspx
> Cheers!
> MB
>
> "md" <someone@.microsoft.com> wrote in message
> news:uDac9PDfHHA.5056@.TK2MSFTNGP02.phx.gbl...
>> Hi all -
>> I am working with the DBA's to do some DR testing to see how to recover
>> the Master db if it became corrupted or unusable. We found a bunch of
>> links about doing this, but nothing seems to work. We used the SQL Server
>> 2005 setup.exe method that MS seems to indicate is the way to do it, but
>> it bombs with no error and does nothing. We then just ran setup and went
>> through the steps, and when it does it's pre-installation checking, it
>> complains that we are trying to change the edition. I am guessing at this
>> point this is because we installed SP2, and are trying to recover using
>> the non-SP CD. Since MS does not allow slipstreaming service packs with
>> SQL Server, how are you supposed to do this?
>> Thanks for any info anyone can provide
>> Matt
>>
>

DR Testing

Hi all -
I am working with the DBA's to do some DR testing to see how to recover the
Master db if it became corrupted or unusable. We found a bunch of links
about doing this, but nothing seems to work. We used the SQL Server 2005
setup.exe method that MS seems to indicate is the way to do it, but it bombs
with no error and does nothing. We then just ran setup and went through the
steps, and when it does it's pre-installation checking, it complains that we
are trying to change the edition. I am guessing at this point this is
because we installed SP2, and are trying to recover using the non-SP CD.
Since MS does not allow slipstreaming service packs with SQL Server, how are
you supposed to do this?
Thanks for any info anyone can provide
MattHello Matt,
Here you go:
http://msdn2.microsoft.com/en-us/library/ms190679.aspx
http://msdn2.microsoft.com/en-us/library/ms175535.aspx
http://msdn2.microsoft.com/en-us/library/ms190190.aspx
http://msdn2.microsoft.com/en-us/library/ms191431.aspx
Cheers!
MB
"md" <someone@.microsoft.com> wrote in message
news:uDac9PDfHHA.5056@.TK2MSFTNGP02.phx.gbl...
> Hi all -
> I am working with the DBA's to do some DR testing to see how to recover
> the Master db if it became corrupted or unusable. We found a bunch of
> links about doing this, but nothing seems to work. We used the SQL Server
> 2005 setup.exe method that MS seems to indicate is the way to do it, but
> it bombs with no error and does nothing. We then just ran setup and went
> through the steps, and when it does it's pre-installation checking, it
> complains that we are trying to change the edition. I am guessing at this
> point this is because we installed SP2, and are trying to recover using
> the non-SP CD. Since MS does not allow slipstreaming service packs with
> SQL Server, how are you supposed to do this?
> Thanks for any info anyone can provide
> Matt
>|||Thanks MB. We had found some of these already, but not all. I forwarded them
to the DBA to take a look.
Thanks again
Matt
"MB" <MB@.MB.com> wrote in message
news:%23K4VhcDfHHA.4916@.TK2MSFTNGP06.phx.gbl...
> Hello Matt,
> Here you go:
> http://msdn2.microsoft.com/en-us/library/ms190679.aspx
> http://msdn2.microsoft.com/en-us/library/ms175535.aspx
> http://msdn2.microsoft.com/en-us/library/ms190190.aspx
> http://msdn2.microsoft.com/en-us/library/ms191431.aspx
> Cheers!
> MB
>
> "md" <someone@.microsoft.com> wrote in message
> news:uDac9PDfHHA.5056@.TK2MSFTNGP02.phx.gbl...
>sql

DPE parameters

I'm creating a DPE to accept a serialized dataset as input to my
report at runtime. But I can't get the parameters working correctly
in VB. I assume the reporting service has some mechanism to set the
parameters, but what is it?
I have the readonly property Parameters that implements
IDbCommand.Parameters. But, it's readonly. So how does the property
get a value to start with?
ThanksIf the extension implements the required interfaces, RS will call the
parameter collection (IDataParameterCollection) Add method automatically
when the report is processed. As a prerequisite, the parameter has to be
declared as a query-level parameter. If it is only report-level param, it
won't be passed.
The sample data extension that comes with RS should get you started. I would
suggest you debug the extension to learn how it works. The easiest way to do
this is to add the extension to your RS solution.
Accidentally, I implemented a custom data extension to support reporting of
serialized or saved to files ADO.NET datasets that you may find useful.
http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=B8468707-56EF-4864-AC51-D83FC3273FE5
--
Hope this helps.
---
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
http://www.prologika.com
"Steven" <montgoss@.hotmail.com> wrote in message
news:a73f4c07.0408060918.60dc6eb4@.posting.google.com...
> I'm creating a DPE to accept a serialized dataset as input to my
> report at runtime. But I can't get the parameters working correctly
> in VB. I assume the reporting service has some mechanism to set the
> parameters, but what is it?
> I have the readonly property Parameters that implements
> IDbCommand.Parameters. But, it's readonly. So how does the property
> get a value to start with?
> Thanks|||"Teo Lachev" <teo@.nospam.prologika.com> wrote in message news:<eh9vH1#eEHA.3428@.TK2MSFTNGP11.phx.gbl>...
> As a prerequisite, the parameter has to be
> declared as a query-level parameter. If it is only report-level param, it
> won't be passed.
I want to make sure I understand this. This means that I can't simply
define the parameter in the report designer. I have to also define it
in my DPE? And I do this via the IDbCommandAnalysis.GetParameters
implementation? Or is that simply for prompting the user at design
time for parameter?
Thx.|||Steven,
Please find my comments inline?
--
Hope this helps.
---
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
http://www.prologika.com
"Steven" <montgoss@.hotmail.com> wrote in message
news:a73f4c07.0408090515.8688bff@.posting.google.com...
> "Teo Lachev" <teo@.nospam.prologika.com> wrote in message
news:<eh9vH1#eEHA.3428@.TK2MSFTNGP11.phx.gbl>...
> > As a prerequisite, the parameter has to be
> > declared as a query-level parameter. If it is only report-level param,
it
> > won't be passed.
> I want to make sure I understand this. This means that I can't simply
> define the parameter in the report designer.
Teo: No, what I was saying is that the parameter has to be defined as a
query (dataset)-level perameter in order to be passed to the custom database
extension. Just defining a parameter as a report-level parameter (Reports
menu->Parameters) is not enough.
I have to also define it
> in my DPE?
Teo: You don't define your parameters in the custom database extension.
Instead, RS (report designer during design time, Report Server during
runtime) will pass them to your extension.
And I do this via the IDbCommandAnalysis.GetParameters
> implementation? Or is that simply for prompting the user at design
> time for parameter?
Teo: Yes, IDbCommandAnalysis is optional and it is useful only during design
time to prompt the report author for parameters. For example, if you may use
a query statement like this:
select * from ... where given_column = @.some_value
In IDbCommandAnalysis.GetParameters you can parse the query statement,
discover that it contains a parameter called some_value and create a new
parameters collection and pass it back. The Report Designer then will
display the parameter collection.
> Thx.|||Thanks for your help so far.
Do you know why your sample doesn't automatically populate the fields
toolbox with values like the FSI sample does?|||Steven,
It should. Moreover, if the dataset has an XML Schema included, the custom
dataset extension should also expose the type of the fields. Did you look at
the readme file accompanying the extension for configuration instructions?
--
Hope this helps.
---
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
http://www.prologika.com
"Steven" <montgoss@.hotmail.com> wrote in message
news:a73f4c07.0408091207.2613bc07@.posting.google.com...
> Thanks for your help so far.
> Do you know why your sample doesn't automatically populate the fields
> toolbox with values like the FSI sample does?|||Yes, I looked at the readme. I get to the point after executing the
query where it says the fields box should now be populated, and it
isn't... This is something my DPE did automatically, but I don't see
how it did it or why yours doesn't seem to.
Just now, I clicked the "..." next to the dataset list and I got an
error. "Could not generate a list of fields for the query. Check the
query syntax or click Refresh Fields on the query toolbar. The path is
not of a legal form". Sure enough, after I clicked "Refresh Fields",
it populated the fields box. Any idea why it doesn't refresh fields
automatically? It seems like the illegal path is a reference to the
@.DataSource param which wasn't yet set(since I hadn't executed the
query).
Thanks.
"Teo Lachev" <teo@.nospam.prologika.com> wrote in message news:<#wNp8AlfEHA.2764@.TK2MSFTNGP11.phx.gbl>...
> Steven,
> It should. Moreover, if the dataset has an XML Schema included, the custom
> dataset extension should also expose the type of the fields. Did you look at
> the readme file accompanying the extension for configuration instructions?
> --
> Hope this helps.
> ---
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> http://www.prologika.com
>
> "Steven" <montgoss@.hotmail.com> wrote in message
> news:a73f4c07.0408091207.2613bc07@.posting.google.com...
> > Thanks for your help so far.
> >
> > Do you know why your sample doesn't automatically populate the fields
> > toolbox with values like the FSI sample does?|||Do you specify Nothing as a query text or the ADO.NET table name?
If yes, please send me your serialized ADO.NET dataset (remove nospam from
my e-mail address). I will be happy to look at it.
--
Hope this helps.
---
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
http://www.prologika.com
"Steven" <montgoss@.hotmail.com> wrote in message
news:a73f4c07.0408100558.50830c01@.posting.google.com...
> Yes, I looked at the readme. I get to the point after executing the
> query where it says the fields box should now be populated, and it
> isn't... This is something my DPE did automatically, but I don't see
> how it did it or why yours doesn't seem to.
> Just now, I clicked the "..." next to the dataset list and I got an
> error. "Could not generate a list of fields for the query. Check the
> query syntax or click Refresh Fields on the query toolbar. The path is
> not of a legal form". Sure enough, after I clicked "Refresh Fields",
> it populated the fields box. Any idea why it doesn't refresh fields
> automatically? It seems like the illegal path is a reference to the
> @.DataSource param which wasn't yet set(since I hadn't executed the
> query).
> Thanks.
> "Teo Lachev" <teo@.nospam.prologika.com> wrote in message
news:<#wNp8AlfEHA.2764@.TK2MSFTNGP11.phx.gbl>...
> > Steven,
> >
> > It should. Moreover, if the dataset has an XML Schema included, the
custom
> > dataset extension should also expose the type of the fields. Did you
look at
> > the readme file accompanying the extension for configuration
instructions?
> >
> > --
> > Hope this helps.
> >
> > ---
> > Teo Lachev, MCSD, MCT
> > Author: "Microsoft Reporting Services in Action"
> > http://www.prologika.com
> >
> >
> > "Steven" <montgoss@.hotmail.com> wrote in message
> > news:a73f4c07.0408091207.2613bc07@.posting.google.com...
> > > Thanks for your help so far.
> > >
> > > Do you know why your sample doesn't automatically populate the fields
> > > toolbox with values like the FSI sample does?|||Yes, I was using "Nothing". I also tried "SalesOrderHeader" with the
same result. I'm using the EntitySalesOrder.xsd from your sample when
doing this.(I assume I don't need to send that to you)
Is it maybe some configuration error on my machine?
Thanks,
Steven
"Teo Lachev" <teo@.nospam.prologika.com> wrote in message news:<ukBywqufEHA.904@.TK2MSFTNGP09.phx.gbl>...
> Do you specify Nothing as a query text or the ADO.NET table name?
> If yes, please send me your serialized ADO.NET dataset (remove nospam from
> my e-mail address). I will be happy to look at it.
> --
> Hope this helps.
> ---
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> http://www.prologika.com|||So, when you run the query in the Generic Query Designer what columns do you
see in the results grid?
--
Hope this helps.
---
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
http://www.prologika.com
"Steven" <montgoss@.hotmail.com> wrote in message
news:a73f4c07.0408110902.4a0007c3@.posting.google.com...
> Yes, I was using "Nothing". I also tried "SalesOrderHeader" with the
> same result. I'm using the EntitySalesOrder.xsd from your sample when
> doing this.(I assume I don't need to send that to you)
> Is it maybe some configuration error on my machine?
> Thanks,
> Steven
> "Teo Lachev" <teo@.nospam.prologika.com> wrote in message
news:<ukBywqufEHA.904@.TK2MSFTNGP09.phx.gbl>...
> > Do you specify Nothing as a query text or the ADO.NET table name?
> >
> > If yes, please send me your serialized ADO.NET dataset (remove nospam
from
> > my e-mail address). I will be happy to look at it.
> >
> > --
> > Hope this helps.
> >
> > ---
> > Teo Lachev, MCSD, MCT
> > Author: "Microsoft Reporting Services in Action"
> > http://www.prologika.com|||SalesOrderID, CustomerID, PurchaseOrderNumber and OrderDate.
Steven
"Teo Lachev" <teo@.nospam.prologika.com> wrote in message news:<uL2dV18fEHA.2984@.tk2msftngp13.phx.gbl>...
> So, when you run the query in the Generic Query Designer what columns do you
> see in the results grid?
> --
> Hope this helps.
> ---
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> http://www.prologika.com|||When you click the Refresh Fields button on the Data tab toolbar do you see
the same fields?
--
Hope this helps.
---
Teo Lachev, MCSD, MCT
Author: "Microsoft Reporting Services in Action"
http://www.prologika.com
"Steven" <montgoss@.hotmail.com> wrote in message
news:a73f4c07.0408120920.70ea1d42@.posting.google.com...
> SalesOrderID, CustomerID, PurchaseOrderNumber and OrderDate.
> Steven
> "Teo Lachev" <teo@.nospam.prologika.com> wrote in message
news:<uL2dV18fEHA.2984@.tk2msftngp13.phx.gbl>...
> > So, when you run the query in the Generic Query Designer what columns do
you
> > see in the results grid?
> >
> > --
> > Hope this helps.
> >
> > ---
> > Teo Lachev, MCSD, MCT
> > Author: "Microsoft Reporting Services in Action"
> > http://www.prologika.com|||Yes, and then they also show up in the fields box.
"Teo Lachev" <teo@.nospam.prologika.com> wrote in message news:<OTdWdVJgEHA.3964@.TK2MSFTNGP12.phx.gbl>...
> When you click the Refresh Fields button on the Data tab toolbar do you see
> the same fields?
> --
> Hope this helps.
> ---
> Teo Lachev, MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> http://www.prologika.com
>
> "Steven" <montgoss@.hotmail.com> wrote in message
> news:a73f4c07.0408120920.70ea1d42@.posting.google.com...
> > SalesOrderID, CustomerID, PurchaseOrderNumber and OrderDate.
> >
> > Steven
> >
> > "Teo Lachev" <teo@.nospam.prologika.com> wrote in message
> news:<uL2dV18fEHA.2984@.tk2msftngp13.phx.gbl>...
> > > So, when you run the query in the Generic Query Designer what columns do
> you
> > > see in the results grid?
> > >
> > > --
> > > Hope this helps.
> > >
> > > ---
> > > Teo Lachev, MCSD, MCT
> > > Author: "Microsoft Reporting Services in Action"
> > > http://www.prologika.com|||I get the same behavior with my custom DPE. I have an ADO.net dataset. The
designer shows the columns, but the fields list is empty until I click the
refresh fields button. My dataset is named "NewDataSet" and my table is
named "ResultTable". Is the table name supposed to be set to Nothing?
Was there resolution to this thread?
-David
"Steven" wrote:
> Yes, and then they also show up in the fields box.
> "Teo Lachev" <teo@.nospam.prologika.com> wrote in message news:<OTdWdVJgEHA.3964@.TK2MSFTNGP12.phx.gbl>...
> > When you click the Refresh Fields button on the Data tab toolbar do you see
> > the same fields?
> >
> > --
> > Hope this helps.
> >
> > ---
> > Teo Lachev, MCSD, MCT
> > Author: "Microsoft Reporting Services in Action"
> > http://www.prologika.com
> >
> >
> > "Steven" <montgoss@.hotmail.com> wrote in message
> > news:a73f4c07.0408120920.70ea1d42@.posting.google.com...
> > > SalesOrderID, CustomerID, PurchaseOrderNumber and OrderDate.
> > >
> > > Steven
> > >
> > > "Teo Lachev" <teo@.nospam.prologika.com> wrote in message
> > news:<uL2dV18fEHA.2984@.tk2msftngp13.phx.gbl>...
> > > > So, when you run the query in the Generic Query Designer what columns do
> > you
> > > > see in the results grid?
> > > >
> > > > --
> > > > Hope this helps.
> > > >
> > > > ---
> > > > Teo Lachev, MCSD, MCT
> > > > Author: "Microsoft Reporting Services in Action"
> > > > http://www.prologika.com
>

Download Link of SQL Express 2005 not working

When I click Download, it show NOT FOUND

What happened ?

Hi,

Download it from http://msdn.microsoft.com/vstudio/express/sql/download/ this link is working properly.

Hemantgiri S. Goswami

Downgrade a SQL 2K5 D.B. TO SQL 2K

Hi, I am working on a test installation of SQL 2K5 but I need to copy a D.B. from SQL 2K5 to a SQL 2K. I tried with backup but the restore in SQL 2K does not work, anyone can help me?

Many thanks,

Fabio.

Hi,

either import the data from SQL Server 2000 or script out the structure and the data (which would be some more work to do) Backups made in SQL Server 2005 are not readable in SQL Server 2000.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks Jens,

the D.B. is too big (about 200 tables) and I have no network access to make an import.

I hoped that was possible to restore it from sql 2k5 to sql 2k ...

I think I have to install a sql2k5 instance on my developement PC.

Fabio.

|||For the data transfer you must have to go import/export route and for the schema you can script the database so.

doubt with sql and an store procedure

I'm working with the stored procedure editor of the Visual Web Developer, and I have this:
ALTER PROCEDURE dbo.ClasificacionSelectTodas
(
@.visibilidad bit = 1
)
AS
SET NOCOUNT ON
SELECT Clas_Id, Clas_Madre, Clas_Titulo, Clas_Descripcion, Clas_Prioridad, Clas_Visibilidad
FROM Clasificacion
WHERE (Clas_Visibilidad = @.visibilidad)
As you see, if I don't set any value to "@.visibilidad" it returns me the registries where visibilidad = 1
But what I want is that if I don't set any value to visibilidad, itturns to me all the registries. I was trying giving a default value tovisibilidad like "*" o "?", but it gives me an error.
Any idea?
Thanks
ALTER PROCEDURE dbo.ClasificacionSelectTodas
(
@.visibilidad bit = null
)
AS
SET NOCOUNT ON
SELECT Clas_Id, Clas_Madre, Clas_Titulo, Clas_Descripcion, Clas_Prioridad, Clas_Visibilidad
FROM Clasificacion
WHERE (Clas_Visibilidad = IsNull(@.visibilidad,Clas_Visibilidad))
This will compare Clas_Cisibilidad to the variable passed in (if not null) or with itself (which will always be true).|||Thanks douglas, it works great
Congratulations for your book!
|||Glad it helped.
Also, I am actually working on a new book, tentatively titledStreamlined Web Forms Development. Should be out by ASP.NET 2.0 release, and will make a great stocking suffer<g>.|||I'm sure it will be highly interesting, I'll wait for it ;)

doubt about sqlserver data types

I'm working with sqlserver express 2005, and I have a lot of doubts about what sqlserver data types use. More exactly my doubt is about text types... nchar, nvarchar, varchar... what are the differences?

thanks.::More exactly my doubt is about text types... nchar, nvarchar, varchar... what are the
::differences?

I really hate to tell you, but there is a documentation for SQL Server that has exact definitions of every data type.

double loop in stored procedure

Dear All,

Im working on a stored procedure that meant to mail out users some of their action items daily.

The procedure has a double loop, first the user ids and user email addresses are selected into a table, then the outer loop cycles through the user ids and selects relevant action items to another table. The inner loop then cycles through these action items and at the end of each outer loop a string is mailed out.

Problem is that as the outer loop selects the relevant items for a user, the table holding the action items basically gets filled with more and more records and the inner loop then adds every item in the table to the string that gets mailed out, ending up with more and more items going to all the users.

I have tried to delete all records from the actionItems table at the end of each outer loop after the content of the action Items are mailed out, however this seems to keep the actionItems table empty at all times.

Not sure if this description is clear enough but I cant see where Im going wrong in terms of approach.

Any ideas?I would suggest posting your SP here, so that we can check out what is going on in the T-SQL code.|||Any TSQL post that uses the word "loop" that frequently can't be good.|||Actually it's sorted, just added a variable that picks up the id of the last action item being added to the e-mail, then the count to add action items to the next e-mail starts from there + 1 AND also I had set this counter to 0 at the start as it would not start the loops while not initialised. Cheers|||Whatever. Continue merrilly down your path to the dark side...|||Actually it's sorted, just added a variable that picks up the id of the last action item being added to the e-mail, then the count to add action items to the next e-mail starts from there + 1 AND also I had set this counter to 0 at the start as it would not start the loops while not initialised. CheersHave you tried dropping charcoal briquettes or real cotton into fuming nitric acid?

-PatP

Don't want to show any zeros

The totaling is working fine but I am getting (0) if there is no "First".
How can I substitute the (0) for "".
=Sum(iif(Fields!Shift_Worked.Value="First",1,0))
Thank you for any suggestions offered
Frank=iif(
Sum(iif(Fields!Shift_Worked.Value="First",1,0)) > 0,
Sum(iif(Fields!Shift_Worked.Value="First",1,0)),
""
)
"Frank" wrote:
> The totaling is working fine but I am getting (0) if there is no "First".
> How can I substitute the (0) for "".
> =Sum(iif(Fields!Shift_Worked.Value="First",1,0))
> Thank you for any suggestions offered
> Frank
>|||Jimbo,
Thank you very much, it works great.
"Jimbo" wrote:
> =iif(
> Sum(iif(Fields!Shift_Worked.Value="First",1,0)) > 0,
> Sum(iif(Fields!Shift_Worked.Value="First",1,0)),
> ""
> )
>
> "Frank" wrote:
> > The totaling is working fine but I am getting (0) if there is no "First".
> > How can I substitute the (0) for "".
> >
> > =Sum(iif(Fields!Shift_Worked.Value="First",1,0))
> >
> > Thank you for any suggestions offered
> >
> > Frank
> >

Don't want to show (0) when running =Sum(iif

The totaling is working fine but I am getting (0) if there is no "First".
How can I substitute the (0) for "".
=Sum(iif(Fields!Shift_Worked.Value="First",1,0))
Thank you for any suggestions offered
FrankI got a similar problem lately. Try using a report function like :
Public Function IsFirst(tehtext as String) as Integer
If((tehtext ="First")
Return 1
Else
Return 0
End If
End Function
Then use it in your expression like this :
=IIf(Sum(Code.IsFirst(Fields!Shift_Worked.Value) > 0),
Sum(Code.IsFirst(Fields!Shift_Worked.Value), "")
I hope that helps...
"Frank" wrote:
> The totaling is working fine but I am getting (0) if there is no "First".
> How can I substitute the (0) for "".
> =Sum(iif(Fields!Shift_Worked.Value="First",1,0))
> Thank you for any suggestions offered
> Frank

Dont display the field if it contains a zero value

I'm working on a report for accounting. Usually debit and credit prob. I don't want to display the field if it contains zero. It creates a gap on my reports and want to avoid it.
Anyone who can help?
Thanks.Using CR 8.5 and RDC, each field has a setting called 'SuppressIfZero' and one called 'SuppressIfBlank'. As the name implies, setting the 'SuppressIfZero' to True will suppress the field if the value is Zero, setting the 'SuppressIfBlank' to True will suppress the field if it's blank.|||I did what you said but I still get a gap between my text. How can I eliminate it?

Thanks.|||Try to put the field in a separate section (If possible), and Suppress section if that value is blank.|||Hi

try suppressing the field or use a formula

if (fieldname) = "0" then "No Data"

I was working on the same thing in crystal reports 9 and got up to this finally.

c ya

Domain User Groups

Hi

Im currently working on a intranet and trying to set up some security. The intranet acesses a SQL server 2000 database. I would like to know if there is a stored procedure(or other way) of returning all the domain groups that a user belongs to when passed the users NT login. I found xp_enumgroups which returns all the groups on the domain and also xp_logininfo which returns the users of a passed domain group. These are usful but i need to just pass the NT username and return all the Domain Groups. Any thoughts, ideas would be great!

CheersI don't know of any way to do this using Microsoft supplied code in SQL Server. The code could certainly be written, but I think it is much easier to do at the client side than on the server.

-PatP

Domain group logins failing on SQL 2k5 workgroup

This question is regarding a brand new out-of-the-box SQL Server 2005 Workgroup Edition install. The old SQL Server 2000 server is working properly with regard to the issue we're having:
We are using Windows Authentication, and have created SQL logins for about

40 different groups on our domain. We've given those logins the appropriate

permissions on the databases they're supposed to be able to access.

The SQL Server is not a domain controller, but is a member of the domain, and domain logins do work for Windows-login purposes on this box.
The problem is that when users try to connect to the SQL server, they are denied access. An error 18456 is thrown, and logged in the Application event log

stating "Login failed for user OURDOMAIN\theuser" (example values). The

domain user is properly a member of group added as a login to SQL Server, and we've

confirmed that there are not conflicting permissions that would deny those

users access via another route. These same groups are working fine on the SQL Server 2000 box.
This is only a problem for domain-based groups. If we create a local group

on the SQL server machine, through Computer Management -> Local Users and

Groups, then make the same domain users a member of THAT group, and finally then

follow the same process to add that local group to SQL Server Logins and set

the database privileges, it works!!
Our group memberships change frequently, and are used for a lot more than

just SQL server permissions. So, using local groups and maintaining

membership in both places is not really feasible. Any ideas why a local

machine group containing domain user accounts would work fine, but a domain

group containing the same accounts would not?
Thanks in advance.
Hi,

see if the default database defined for the users / groups ius available and they are granted access to the database. If not they will be denied access to the server and will get the error message posted by you. Did you try to create a single Windows and login with this user ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||Single user: Yes. Creating individual logins for domain users works fine. It is only logins for domain groups that are not working.

Default database: The users are connecting via ODBC connections, and the default database is set correctly.

It doesn't seem to be related to any database selection issues at all. Within a single database, if we grant access to the individual user account, or a local machine group that the user is a part of, everything works fine. Grant them access via a domain group, and it denies login. This is not something we've encountered before, and is making me wonder if there is some weird, poorly-documented restriction in the Workgroup Edition...|||

Please post the error as it is printed in the errorlog file of SQL Server (the ones under MSSQL\...\LOG\ERRORLOG*). Post both the error messages and the error numbers and states - the states are important.

Thanks
Laurentiu

|||(Domain name/IP munged for privacy reasons. Can send via private message if required for some reason.)

With group OURDOMAIN\SecGroupA created on the domain controller, and user 'kswain' made a member of the group. We create a SQL Server login for OURDOMAIN\SecGroupA and get:

2006-12-27 10:45:02.50 Logon Error: 18456, Severity: 14, State: 11.
2006-12-27 10:45:02.50 Logon Login failed for user 'OURDOMAIN\kswain'. [CLIENT: xxx.xxx.xxx.xxx]

With local group TestLocalGroup created on the SQL Server machine, and user 'OURDOMAIN\kswain' added as a member: We create a SQL Server login for SERVERMACHINE\TestLocalGroup using the same process as previously, and it works fine. We don't even have to log the end-user account out of the application... it works as soon as we authorize the local group.|||

Hi,

Does this error comes when you access from your Application or via Query Analyzer ? Are you able to login via Query Analyzer?

What application you are running !? A web application ? Ensure IIS Permission is also properly set refer below KB

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

What about connection string in your application ?

Hemantgiri S. Goswami

|||The login failure occurs both from the application and from Query Analyzer using any non-Administrator account.

Our testbed application at the moment is actually just an Access database, using the built-in Windows SQL Server ODBC driver, set up as a Machine DSN. When our main app didn't work, we created the simplest method we could think of to try and connect. We are not using IIS for this at all. We know the DSN itself is set up correctly since it works if the user is explicitly added, or is part of a SQL Server machine-local group.

--
One additional thing we've discovered in the last 24 hours. It still does NOT work if you add a domain group to a local group. So the issue seems to be one of domain group membership resolution. In other words, if we authorize SQLServer\LocalGroupA:

* If OURDOMAIN\userA is a member of SQLServer\LocalGroupA, OURDOMAIN\userA login => OK

* If OURDOMAIN\userA is a member of OURDOMAIN\DomainGroupA, and OURDOMAIN\DomainGroupA is a member of SQLServer\LocalGroupA, OURDOMAIN\userA login => FAIL!

Other thoughts we're having that might be somehow relevant, but we can't seem to get around:

1) The domain is mixed Win2000 and Win2003. The SQL Server 2k5 is running on a Win2003 machine that is not a domain controller, but is a domain member.

2) Our AD domain name has a hyphen in it, both in NetBIOS and FQDN (i.e. OUR-DOMAIN and cleveland.our-domain.local)

3) The non-administrative users are accessing the application server via Terminal Services.

None of the above should make a difference (and don't have any problems with SQL Server 2000), but we're really grasping at straws at this point...|||

Can you see if LookupAccountName works for the group name? If you have a small application called name2sid, you could use it to check this. Or you could use something similar to my CLR function from http://blogs.msdn.com/lcris/archive/2005/09/26/474202.aspx.

If this function works ok, then I suggest to open a report on the site indicated in the sticky thread at the top of this forum. You can start the server with the -y18456 parameter, to have it generate a memory dump, and you can attach the dump to the report.

Thanks
Laurentiu

|||I don't have name2sid, but I have the SysInternals "psGetSid" utility, which should do the same thing. Run against OURDOMAIN\TestGroupA, it returns a good SID, so that much is working. If your function or name2sid does something different than this utility, to your knowledge, please let me know and I can try to implement that instead.

I'm not familiar with the -y18456 parameter. I just restarted the SQL Server service with that flag included in the Startup Parameters, but don't see a dump anywhere, or anything especially instructive in the event log. Can you tell me what I should be looking for after restarting with that flag? Once I can find that, I'll open a report on the Connect site. Thanks!|||Please disregard previous request -- I see that it only outputs dumps when that specific error is thrown. Got it, and attaching it to a Connect bug now. Thanks!|||Just for closure on this thread, this issue has been moved to a Connect feedback/bug report. ID is 248615 and can be found here:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=248615|||

Hi,

Did you find a fix for this? I think we're having the same problem. I talked to a consultant who thought it was something with our domain since we were running windows 2000 and didnt have the windows DNS running as part of our domain. But everything was working except sql server so I should have known better. So we upgraded our domain controller and spent all kinds of money and it still doesn't work!! Please let me know if you figured out how to fix this!! None of our AD groups are working as logins. Only users and groups on the sql server machine.

Bob Coleman

|||No fix or workaround has been identified yet. Nobody at Microsoft has tagged the Connect bug referenced above, if it has even been reviewed yet. I'm trying to be patient, figuring that people were on vacation over the holidays.

At the moment, we're just maintaining machine-local accounts with the appropriate domain users. Hopefully we'll get some kind of response shortly!|||

We have received your feedback report. When we'll have an update on this issue, we'll update the report.

I am not familiar with the PsSid tool - could you point me to the link from which you downloaded it?

The -y argument can be used with any error number, to make the server produce a dump whenever the error is raised.

Thanks
Laurentiu

|||Certainly! psGetSid was referenced on this page: http://www.microsoft.com/technet/sysinternals/utilities/psgetsid.mspx

It's part of the SysInternals command-line suite that MS acquired earlier this year. Nifty stuff.

Thanks!

Domain group logins failing on SQL 2k5 workgroup

This question is regarding a brand new out-of-the-box SQL Server 2005 Workgroup Edition install. The old SQL Server 2000 server is working properly with regard to the issue we're having:
We are using Windows Authentication, and have created SQL logins for about

40 different groups on our domain. We've given those logins the appropriate

permissions on the databases they're supposed to be able to access.

The SQL Server is not a domain controller, but is a member of the domain, and domain logins do work for Windows-login purposes on this box.
The problem is that when users try to connect to the SQL server, they are denied access. An error 18456 is thrown, and logged in the Application event log

stating "Login failed for user OURDOMAIN\theuser" (example values). The

domain user is properly a member of group added as a login to SQL Server, and we've

confirmed that there are not conflicting permissions that would deny those

users access via another route. These same groups are working fine on the SQL Server 2000 box.
This is only a problem for domain-based groups. If we create a local group

on the SQL server machine, through Computer Management -> Local Users and

Groups, then make the same domain users a member of THAT group, and finally then

follow the same process to add that local group to SQL Server Logins and set

the database privileges, it works!!
Our group memberships change frequently, and are used for a lot more than

just SQL server permissions. So, using local groups and maintaining

membership in both places is not really feasible. Any ideas why a local

machine group containing domain user accounts would work fine, but a domain

group containing the same accounts would not?
Thanks in advance.
Hi,

see if the default database defined for the users / groups ius available and they are granted access to the database. If not they will be denied access to the server and will get the error message posted by you. Did you try to create a single Windows and login with this user ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||Single user: Yes. Creating individual logins for domain users works fine. It is only logins for domain groups that are not working.

Default database: The users are connecting via ODBC connections, and the default database is set correctly.

It doesn't seem to be related to any database selection issues at all. Within a single database, if we grant access to the individual user account, or a local machine group that the user is a part of, everything works fine. Grant them access via a domain group, and it denies login. This is not something we've encountered before, and is making me wonder if there is some weird, poorly-documented restriction in the Workgroup Edition...|||

Please post the error as it is printed in the errorlog file of SQL Server (the ones under MSSQL\...\LOG\ERRORLOG*). Post both the error messages and the error numbers and states - the states are important.

Thanks
Laurentiu

|||(Domain name/IP munged for privacy reasons. Can send via private message if required for some reason.)

With group OURDOMAIN\SecGroupA created on the domain controller, and user 'kswain' made a member of the group. We create a SQL Server login for OURDOMAIN\SecGroupA and get:

2006-12-27 10:45:02.50 Logon Error: 18456, Severity: 14, State: 11.
2006-12-27 10:45:02.50 Logon Login failed for user 'OURDOMAIN\kswain'. [CLIENT: xxx.xxx.xxx.xxx]

With local group TestLocalGroup created on the SQL Server machine, and user 'OURDOMAIN\kswain' added as a member: We create a SQL Server login for SERVERMACHINE\TestLocalGroup using the same process as previously, and it works fine. We don't even have to log the end-user account out of the application... it works as soon as we authorize the local group.|||

Hi,

Does this error comes when you access from your Application or via Query Analyzer ? Are you able to login via Query Analyzer?

What application you are running !? A web application ? Ensure IIS Permission is also properly set refer below KB

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

What about connection string in your application ?

Hemantgiri S. Goswami

|||The login failure occurs both from the application and from Query Analyzer using any non-Administrator account.

Our testbed application at the moment is actually just an Access database, using the built-in Windows SQL Server ODBC driver, set up as a Machine DSN. When our main app didn't work, we created the simplest method we could think of to try and connect. We are not using IIS for this at all. We know the DSN itself is set up correctly since it works if the user is explicitly added, or is part of a SQL Server machine-local group.

--
One additional thing we've discovered in the last 24 hours. It still does NOT work if you add a domain group to a local group. So the issue seems to be one of domain group membership resolution. In other words, if we authorize SQLServer\LocalGroupA:

* If OURDOMAIN\userA is a member of SQLServer\LocalGroupA, OURDOMAIN\userA login => OK

* If OURDOMAIN\userA is a member of OURDOMAIN\DomainGroupA, and OURDOMAIN\DomainGroupA is a member of SQLServer\LocalGroupA, OURDOMAIN\userA login => FAIL!

Other thoughts we're having that might be somehow relevant, but we can't seem to get around:

1) The domain is mixed Win2000 and Win2003. The SQL Server 2k5 is running on a Win2003 machine that is not a domain controller, but is a domain member.

2) Our AD domain name has a hyphen in it, both in NetBIOS and FQDN (i.e. OUR-DOMAIN and cleveland.our-domain.local)

3) The non-administrative users are accessing the application server via Terminal Services.

None of the above should make a difference (and don't have any problems with SQL Server 2000), but we're really grasping at straws at this point...|||

Can you see if LookupAccountName works for the group name? If you have a small application called name2sid, you could use it to check this. Or you could use something similar to my CLR function from http://blogs.msdn.com/lcris/archive/2005/09/26/474202.aspx.

If this function works ok, then I suggest to open a report on the site indicated in the sticky thread at the top of this forum. You can start the server with the -y18456 parameter, to have it generate a memory dump, and you can attach the dump to the report.

Thanks
Laurentiu

|||I don't have name2sid, but I have the SysInternals "psGetSid" utility, which should do the same thing. Run against OURDOMAIN\TestGroupA, it returns a good SID, so that much is working. If your function or name2sid does something different than this utility, to your knowledge, please let me know and I can try to implement that instead.

I'm not familiar with the -y18456 parameter. I just restarted the SQL Server service with that flag included in the Startup Parameters, but don't see a dump anywhere, or anything especially instructive in the event log. Can you tell me what I should be looking for after restarting with that flag? Once I can find that, I'll open a report on the Connect site. Thanks!|||Please disregard previous request -- I see that it only outputs dumps when that specific error is thrown. Got it, and attaching it to a Connect bug now. Thanks!|||Just for closure on this thread, this issue has been moved to a Connect feedback/bug report. ID is 248615 and can be found here:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=248615|||

Hi,

Did you find a fix for this? I think we're having the same problem. I talked to a consultant who thought it was something with our domain since we were running windows 2000 and didnt have the windows DNS running as part of our domain. But everything was working except sql server so I should have known better. So we upgraded our domain controller and spent all kinds of money and it still doesn't work!! Please let me know if you figured out how to fix this!! None of our AD groups are working as logins. Only users and groups on the sql server machine.

Bob Coleman

|||No fix or workaround has been identified yet. Nobody at Microsoft has tagged the Connect bug referenced above, if it has even been reviewed yet. I'm trying to be patient, figuring that people were on vacation over the holidays.

At the moment, we're just maintaining machine-local accounts with the appropriate domain users. Hopefully we'll get some kind of response shortly!|||

We have received your feedback report. When we'll have an update on this issue, we'll update the report.

I am not familiar with the PsSid tool - could you point me to the link from which you downloaded it?

The -y argument can be used with any error number, to make the server produce a dump whenever the error is raised.

Thanks
Laurentiu

|||Certainly! psGetSid was referenced on this page: http://www.microsoft.com/technet/sysinternals/utilities/psgetsid.mspx

It's part of the SysInternals command-line suite that MS acquired earlier this year. Nifty stuff.

Thanks!

Domain group logins failing on SQL 2k5 workgroup

This question is regarding a brand new out-of-the-box SQL Server 2005 Workgroup Edition install. The old SQL Server 2000 server is working properly with regard to the issue we're having:
We are using Windows Authentication, and have created SQL logins for about
40 different groups on our domain. We've given those logins the appropriate
permissions on the databases they're supposed to be able to access. The SQL Server is not a domain controller, but is a member of the domain, and domain logins do work for Windows-login purposes on this box.
The problem is that when users try to connect to the SQL server, they are denied access. An error 18456 is thrown, and logged in the Application event log
stating "Login failed for user OURDOMAIN\theuser" (example values). The
domain user is properly a member of group added as a login to SQL Server, and we've confirmed that there are not conflicting permissions that would deny those
users access via another route. These same groups are working fine on the SQL Server 2000 box.
This is only a problem for domain-based groups. If we create a local group
on the SQL server machine, through Computer Management -> Local Users and
Groups, then make the same domain users a member of THAT group, and finally then follow the same process to add that local group to SQL Server Logins and set
the database privileges, it works!!
Our group memberships change frequently, and are used for a lot more than
just SQL server permissions. So, using local groups and maintaining
membership in both places is not really feasible. Any ideas why a local
machine group containing domain user accounts would work fine, but a domain
group containing the same accounts would not?
Thanks in advance.
Hi,

see if the default database defined for the users / groups ius available and they are granted access to the database. If not they will be denied access to the server and will get the error message posted by you. Did you try to create a single Windows and login with this user ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||Single user: Yes. Creating individual logins for domain users works fine. It is only logins for domain groups that are not working.

Default database: The users are connecting via ODBC connections, and the default database is set correctly.

It doesn't seem to be related to any database selection issues at all. Within a single database, if we grant access to the individual user account, or a local machine group that the user is a part of, everything works fine. Grant them access via a domain group, and it denies login. This is not something we've encountered before, and is making me wonder if there is some weird, poorly-documented restriction in the Workgroup Edition...
|||

Please post the error as it is printed in the errorlog file of SQL Server (the ones under MSSQL\...\LOG\ERRORLOG*). Post both the error messages and the error numbers and states - the states are important.

Thanks
Laurentiu

|||(Domain name/IP munged for privacy reasons. Can send via private message if required for some reason.)

With group OURDOMAIN\SecGroupA created on the domain controller, and user 'kswain' made a member of the group. We create a SQL Server login for OURDOMAIN\SecGroupA and get:

2006-12-27 10:45:02.50 Logon Error: 18456, Severity: 14, State: 11.
2006-12-27 10:45:02.50 Logon Login failed for user 'OURDOMAIN\kswain'. [CLIENT: xxx.xxx.xxx.xxx]

With local group TestLocalGroup created on the SQL Server machine, and user 'OURDOMAIN\kswain' added as a member: We create a SQL Server login for SERVERMACHINE\TestLocalGroup using the same process as previously, and it works fine. We don't even have to log the end-user account out of the application... it works as soon as we authorize the local group.

|||

Hi,

Does this error comes when you access from your Application or via Query Analyzer ? Are you able to login via Query Analyzer?

What application you are running !? A web application ? Ensure IIS Permission is also properly set refer below KB

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

What about connection string in your application ?

Hemantgiri S. Goswami

|||The login failure occurs both from the application and from Query Analyzer using any non-Administrator account.

Our testbed application at the moment is actually just an Access database, using the built-in Windows SQL Server ODBC driver, set up as a Machine DSN. When our main app didn't work, we created the simplest method we could think of to try and connect. We are not using IIS for this at all. We know the DSN itself is set up correctly since it works if the user is explicitly added, or is part of a SQL Server machine-local group.

--
One additional thing we've discovered in the last 24 hours. It still does NOT work if you add a domain group to a local group. So the issue seems to be one of domain group membership resolution. In other words, if we authorize SQLServer\LocalGroupA:

* If OURDOMAIN\userA is a member of SQLServer\LocalGroupA, OURDOMAIN\userA login => OK

* If OURDOMAIN\userA is a member of OURDOMAIN\DomainGroupA, and OURDOMAIN\DomainGroupA is a member of SQLServer\LocalGroupA, OURDOMAIN\userA login => FAIL!

Other thoughts we're having that might be somehow relevant, but we can't seem to get around:

1) The domain is mixed Win2000 and Win2003. The SQL Server 2k5 is running on a Win2003 machine that is not a domain controller, but is a domain member.

2) Our AD domain name has a hyphen in it, both in NetBIOS and FQDN (i.e. OUR-DOMAIN and cleveland.our-domain.local)

3) The non-administrative users are accessing the application server via Terminal Services.

None of the above should make a difference (and don't have any problems with SQL Server 2000), but we're really grasping at straws at this point...
|||

Can you see if LookupAccountName works for the group name? If you have a small application called name2sid, you could use it to check this. Or you could use something similar to my CLR function from http://blogs.msdn.com/lcris/archive/2005/09/26/474202.aspx.

If this function works ok, then I suggest to open a report on the site indicated in the sticky thread at the top of this forum. You can start the server with the -y18456 parameter, to have it generate a memory dump, and you can attach the dump to the report.

Thanks
Laurentiu

|||I don't have name2sid, but I have the SysInternals "psGetSid" utility, which should do the same thing. Run against OURDOMAIN\TestGroupA, it returns a good SID, so that much is working. If your function or name2sid does something different than this utility, to your knowledge, please let me know and I can try to implement that instead.

I'm not familiar with the -y18456 parameter. I just restarted the SQL Server service with that flag included in the Startup Parameters, but don't see a dump anywhere, or anything especially instructive in the event log. Can you tell me what I should be looking for after restarting with that flag? Once I can find that, I'll open a report on the Connect site. Thanks!

|||Please disregard previous request -- I see that it only outputs dumps when that specific error is thrown. Got it, and attaching it to a Connect bug now. Thanks!
|||Just for closure on this thread, this issue has been moved to a Connect feedback/bug report. ID is 248615 and can be found here:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=248615
|||

Hi,

Did you find a fix for this? I think we're having the same problem. I talked to a consultant who thought it was something with our domain since we were running windows 2000 and didnt have the windows DNS running as part of our domain. But everything was working except sql server so I should have known better. So we upgraded our domain controller and spent all kinds of money and it still doesn't work!! Please let me know if you figured out how to fix this!! None of our AD groups are working as logins. Only users and groups on the sql server machine.

Bob Coleman

|||No fix or workaround has been identified yet. Nobody at Microsoft has tagged the Connect bug referenced above, if it has even been reviewed yet. I'm trying to be patient, figuring that people were on vacation over the holidays.

At the moment, we're just maintaining machine-local accounts with the appropriate domain users. Hopefully we'll get some kind of response shortly!
|||

We have received your feedback report. When we'll have an update on this issue, we'll update the report.

I am not familiar with the PsSid tool - could you point me to the link from which you downloaded it?

The -y argument can be used with any error number, to make the server produce a dump whenever the error is raised.

Thanks
Laurentiu

|||Certainly! psGetSid was referenced on this page: http://www.microsoft.com/technet/sysinternals/utilities/psgetsid.mspx

It's part of the SysInternals command-line suite that MS acquired earlier this year. Nifty stuff.

Thanks!

Does the Undo operation work ?

Hi ,

I was working in the SSIS designer and when I found that the DataFlow task I deleted was indeed something I needed, I tried to Undo the operation but Alas the option is not enabled :(

Is there a way we can undo the operations?

as such I guess there is no way u can undo any changes. best possible way, work in Foundation server and keep checking in whenever you feel you are completed.

Does the Undo operation work ?

Hi ,

I was working in the SSIS designer and when I found that the DataFlow task I deleted was indeed something I needed, I tried to Undo the operation but Alas the option is not enabled :(

Is there a way we can undo the operations?

as such I guess there is no way u can undo any changes. best possible way, work in Foundation server and keep checking in whenever you feel you are completed.