Microsoft Releases Synchronization Services CTP

The Microsoft Synchronization Services for ADO.NET v1.0 CTP release appeared without fanfare on January 22, 2006. The release contains "v1.0 early CTP" bits for the sync framework and SQL Server 2005 Compact Edition (SSCE) v3.5, the Orcas successor to the SSCE v3.1 RTM bits, which Microsoft released on January 11, 2006. The current code name for Sync Services is OCS (for Occasionally Connected Systems).

Seems to me to resemble a "stealth release."

For more, see http://oakleafblog.blogspot.com/2007/01/microsoft-releases-synchronization.html.

Oops. Make that January 11, 2007!

--rj

Microsoft recommondation.

I have one server that contains Database server, Application server and
domain controller.
What microsoft recommond to boost up the performance? to separate all the
server or separate only domain controller and make Database and Application
as a one server?
Thanks in advance. urgently need the feedback.
Thanks
Rogers wrote:
> I have one server that contains Database server, Application server
> and domain controller.
> What microsoft recommond to boost up the performance? to separate all
> the server or separate only domain controller and make Database and
> Application as a one server?
> Thanks in advance. urgently need the feedback.
> Thanks
Depends on your application, database, and domain controller
utilization. It's always best to keep the database server separate from
other services/applications to maximize bandwidth. But if your
environment is small, has little activity, and your budget is low, then
a combination may work as long as you have enough memory.
David Gugick - SQL Server MVP
Quest Software
|||Environment is basically Calling Centre and environment is little bit high
and call comes very frequently so that means we have separate Domain
Controller, Application and Database that means we should have three
servers? Am I right.
Thanks
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:e7$vtTMPGHA.3936@.TK2MSFTNGP12.phx.gbl...
> Rogers wrote:
> Depends on your application, database, and domain controller utilization.
> It's always best to keep the database server separate from other
> services/applications to maximize bandwidth. But if your environment is
> small, has little activity, and your budget is low, then a combination may
> work as long as you have enough memory.
> --
> David Gugick - SQL Server MVP
> Quest Software
>
|||Roger wrote:
> Environment is basically Calling Centre and environment is little bit
> high and call comes very frequently so that means we have separate
> Domain Controller, Application and Database that means we should have
> three servers? Am I right.
>
Given the information you provided, three servers sounds like the right
idea.
David Gugick - SQL Server MVP
Quest Software
|||Thanks David...
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:%23G8L9BPPGHA.3888@.TK2MSFTNGP12.phx.gbl...
> Roger wrote:
> Given the information you provided, three servers sounds like the right
> idea.
> --
> David Gugick - SQL Server MVP
> Quest Software
>

Microsoft Access to SQL Server 2005

Hi,

I have a database in MSACCESS 2003 that is 680MB (after compacting) and contains 41 tables.

I tried to import these tables to SQL Server 2005 (express edition) using the :"upsizing wizard" provided in MSACCESS. The wizard works fine but all the tables are not being imported to SQL Server (only 19 tables are getting imported) and the size of the database in SQL Server (the ".mdf file") is 1.03 GB (I have tried using the "shrink" option also) . Further, when I try to open one of the tables (which has 625295 rows and 90 columns) , it takes lot of time to display all records.

So, my problem is do I need to set any options for any of these above issues, I tried to look for any information regarding this but was unsuccessful.

Any help on this will be very much helpful for me!

thanks

Further, when I try to open one of the tables (which has 625295 rows and 90 columns) , it takes lot of time to display all records.

So filter the records by queries and never select so much data to client application ( I hasn't ever seen a user able to deal with such amount of data ), and all will be ok.

only 19 tables are getting imported

And there were no any error message during import?

".mdf file" is 1.03 GB

It is possible, that MSSQL requieres more space to store the data.

|||

Hi,

Thanks for the information

I see then, it is normal for SQL Server 2005 to take some amount of time to display all the records of a table, if the table is huge.

Regarding the import problem, I dont get any error while importing.I wonder why only 19 tables are getting imported (may be due to huge table I have in the database)

Microsoft Access Security

I HAVE CREATED A SECURITY DATABASE USING A NEW WORKGROUP FILE WITH A NEW MDW FILE NAME. THE DATABASE ITSELF CONTAINS SEVERAL GROUPS OF USERS AND SEVERAL USERS. THE DATABASE WORKS AS DESIGNED.
THE PROBLEMS IS IF I OPEN THIS DATABASE USING THE SYSTEM.MDW FILE, THE DATABASE OPENS AND GIVE ME COMPLETE ACCESS TO EVERYTHING.

CAN ANYONE EXPLAIN WHAT IS HAPPENING.

ANY HELP WILL BE APPRECIATED

THANKING YOU IN ADVANCE

JOSEPH FORDDid you give the user Admin a password?

Did you join to the workgroup?|||Originally posted by Brett Kaiser
Did you give the user Admin a password?

Did you join to the workgroup?
I gave the admin a password and then created a new administer with a different name.

When I open the database with the workgroup I created it works fine.
but when I open the database with the system.mdw workgroup it allow me to enter the database. which should not be. I am missing something.

Thanks|||And it doesn't ask you for a password, right?|||Originally posted by Brett Kaiser
And it doesn't ask you for a password, right?

Yes that is correct. The following information I found in Q/A section. What do you make of this.
10. Additionally, you may need manually to remove the Open/Run permission from the database container for the Users group through the security menus or through code. This will prevent someone from opening the database by using another workgroup information file or the default System.mda/mdw. In Microsoft Access 97, the User Level Security Wizard is supposed to remove the Open/Run database permissions for the Users group, but fails to do so. The Access 2000 Security Wizard removes permissions to the point where they are not visible on the security menus, but testing has revealed that in Access 2000 it is possible to open a database by using the default workgroup information file regardless of the menu settings. The cure for both versions of Access is to create a new, empty database while logged on as a member of the Admins group and import all of the objects from the secured database. You should take this step before spending too much time securing objects because Access considers imported objects to be new and loses the permission information that was stored in the source database.|||Yeah..it's a toy...

Don't use the default workgroup...

But you said you removed all of the permissions from Admin (that's what it's opening with), but it doesn't seem to be the case...

You sure your removed Admin from the Admin group?

And made sure it had no permissions?|||Originally posted by Brett Kaiser
Yeah..it's a toy...

Don't use the default workgroup...

But you said you removed all of the permissions from Admin (that's what it's opening with), but it doesn't seem to be the case...

You sure your removed Admin from the Admin group?

And made sure it had no permissions?

I think I have but could be wrong. I have attached a file that I would appreciate your looking at to see if you can see the problelm.

Thanks for your help

Joe Ford|||I think you forgot the attachment...|||Originally posted by Brett Kaiser
I think you forgot the attachment...

Your are right. I have attached it now. Please forgive my senior memo.|||OK,

How about what he permissions are fopr the user group...|||Originally posted by Brett Kaiser
OK,

How about what he permissions are fopr the user group...

ALL USERS ARE PART OF THE USER GROUP AND THAT GROUP HAS NO PERMISSION AT ALL INCLUDING ADMIN.|||Yeah...I figured as much...

Who is the owner of all the objects...Where they all originally created by Admin?|||Originally posted by Brett Kaiser
Yeah...I figured as much...

Who is the owner of all the objects...Where they all originally created by Admin?

Owner is Poweradmin see attached|||What about the other objects (like tables, macros, ect)...don't know if dbowner does it...I think it should...

who owns them?|||Originally posted by Brett Kaiser
What about the other objects (like tables, macros, ect)...don't know if dbowner does it...I think it should...

who owns them?

they are all owned by poweradmin|||Make sure u encrypt ur database using workgroup information file

Also inform u are whitout knowing that even if u create particular
security file for an access database .. .Users group which is default to any *.mdw file will be created and access won't allow u to delete it ...

however make sure you didn't grant any permission to this group

regards ...

Meta-Information about Stored-Procedures

Hi ,

I am looking for meta-information about the return recordset of a
stored-procedure. The procedure returns a resultset that contains columns of
more tables joined together. In all tables, I use, there is a
Record-Creation-Timestamp-Attribute. When joining two or more tables these
attribute-names appear in ther resultset but
i found no way to distinguish them.

I there a way to retrieve meta-information about the result-recordset of
such a stored-procedure?

here some details:

the tables
=======
CREATE TABLE [dbo].[Table1] (
[Table1ID] [int] IDENTITY (1, 1) NOT NULL ,
[FK_Tab2ID] [int] NULL ,
[CreatedAt] [datetime] NULL )

CREATE TABLE [dbo].[Table2] (
[Table2ID] [int] IDENTITY (1, 1) NOT NULL ,
[Description] [varchar] (35) NULL ,
[CreatedAt] [datetime] NULL)

the stored-procedure:
===============

CREATE PROCEDURE dbo.sp_Test_RetrieveData
@.ID int
AS
SET NOCOUNT ON

select * from table1 inner join table2 on (FK_Tab2ID = Table2ID)
where table1.ID = @.ID
GO

the resultset:
==========
Table1ID,FK_Tab2ID,CreatedAt,Table2ID,Description, CreatedAt
(the attribute CreatedAt appears twice.)

--= Posted via Newsfeeds.Com, Uncensored Usenet News =--
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
--== Over 100,000 Newsgroups - 19 Different Servers! =--KG wrote:
> CREATE PROCEDURE dbo.sp_Test_RetrieveData
> @.ID int
> AS
> SET NOCOUNT ON
> select * from table1 inner join table2 on (FK_Tab2ID = Table2ID)
> where table1.ID = @.ID
> GO
> the resultset:
> ==========
> Table1ID,FK_Tab2ID,CreatedAt,Table2ID,Description, CreatedAt
> (the attribute CreatedAt appears twice.)

Try this instead:

CREATE PROCEDURE dbo.sp_Test_RetrieveData
@.ID int
AS
SET NOCOUNT ON

select Table1ID, FK_Tab2ID, Table1.CreatedAt as Table1CreatedAt, Table2ID,
Description, Table2.CreatedAt as Table2CreatedAt
from table1 inner join table2 on (FK_Tab2ID = Table2ID)
where table1.ID = @.ID
GO

you will get resultset:

Table1ID, FK_Tab2ID, Table1CreatedAt, Table2ID, Description, Table2CreatedAt

--
Steve Troxell
Krell Software - Database Tools for MS SQL Server
http://www.krell-software.com|||KG (kg@.greenmail.ch) writes:
> I am looking for meta-information about the return recordset of a
> stored-procedure. The procedure returns a resultset that contains
> columns of more tables joined together. In all tables, I use, there is a
> Record-Creation-Timestamp-Attribute. When joining two or more tables
> these attribute-names appear in ther resultset but i found no way to
> distinguish them.
> I there a way to retrieve meta-information about the result-recordset of
> such a stored-procedure?

It would have helped if you have told in which environment you are working.
Are you using ADO?

In ADO, there are some properties on the Fields on object which may have
this information.

But it is kind of obscure programming to access this data. Better is to
use column aliases. Generally, SELECT * should not be used in production
code.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Metadata about tables

Is there a way to add metadata to tables in a database in either SQL
2000 or 2005, describing what they are for and what their data
contains (just plain text string description) , from a seperate table
that contains teh database table names and a field that might be
called 'Description'?
tia MattRead in Books Online about "Extended properties".
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<ma77g@.clara.co.uk> wrote in message news:1190916619.563956.256400@.19g2000hsx.googlegroups.com...
> Is there a way to add metadata to tables in a database in either SQL
> 2000 or 2005, describing what they are for and what their data
> contains (just plain text string description) , from a seperate table
> that contains teh database table names and a field that might be
> called 'Description'?
> tia Matt
>

Meta Database Design Select Question.

Hi,

I have a Datbase with teh following two tables.

Table 1: default_en_listingsdb
it contains the following fields
ID user_ID Title

Table2:
default_en_listingsdbelements
ID field_name field_value listing_id

listing_ID in table 2 is equal to the ID in table 1.

I am building a search for these two tables where i want to return the ID, user_ID and Title. The table data looks like this.

Table 1:
ID user_ID Title
1 1 Test
2 2 Test2

Table2:
ID field_name field_value listing_id
1 beds 2 2
2 beds 1 1
3 city kingsley 1
4 city kingsley 2

I want to return only the ID's where they contain both beds = 2 and city = kingsley.. I want to do this with on e select statement if possible.

Thanks,I hate this, what Tom Kyte calls the "funky data model". Flexible as you like, but so hard to query (and this is a very simple query!)

Also, data integrity is non-existent, because there can be no database constraint that stops you putting 2 for city or kingsley for beds...

Anyway... </RANT>

select t1.*
from table1 t1, table2 beds, table2 city
where t1.id = beds.listing_id
and beds.field_name = 'beds'
and beds.field_value = '2'
and city.field_name = 'city'
and city.field_value = 'kingsley';

Yuk!|||Thanks, I knew it was going to be ugly, i agree that this data model in some ways really sucks... ohh well off to make this work.. Thanks again|||Originally posted by greengaint
Thanks, I knew it was going to be ugly, i agree that this data model in some ways really sucks... ohh well off to make this work.. Thanks again
Everyone "invents" this data model at some point early in their database careers; well, I'm sure I did once anyway. "Hey, look! With this model we don't have to alter tables or application code ever again! The users can just define their own 'fields' whenever they like!" Then later you find that:
(a) performance sucks very badly, and
(b) you need to write SQL 17 pages long to produce the simplest report, and
(c) the data is full of nonsense like beds='4.2' and city = ' kignsley' and startdate = '31 Feb 2004'... and
(d) nobody likes this system any more

Message Box In Reporting services

Hello,

I am using sql reporting services 2000. I have tried to put a message box in my reports using a VB function. If the report contains 10 pages, the message box pops up 10 times. What do i need to do to make the message box pop up only once during the start of the report? Also, if I click CANCEL(vbOkCancel), the cursor should go back to the parameter box prompting me to enter a parameter again. In this case, I enter a date and check whether it is a MONDAY or not. VB function is as below...

Function CheckDay(ByVal S As DateTime) As Integer
Dim GivenDate as Date
Dim GivenDay as Integer
Dim intMsg as Integer
GivenDate = S
GivenDay = WeekDay(GivenDate)
If NOT GivenDay = 2
intMsg = MsgBox("The selected day is not a Monday", VbOKCancel, "The selected date is not a Monday.")
End IF

Return GivenDay
End Function

Thanks......

I recommend to use the ReportViewer control (www.gotreportviewer.com) of VS 2005 instead and build your own parameter user interface to perform the validation. Once, the validation succeeds, you would use the ReportViewer control to display the report.

The approach you are currently trying won't work. Also keep in mind that the message box pop up will only work when running that report in preview. It won't work for reports deployed on a report server.

-- Robert